Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 17 AUG 2006 12:17:42AM Matthew Crozier wrote:

This is happening in our development system as soon as OleCallMethod or OlePutProperty are called in a program. There don't seem to be SYSOBJ records for any of the OLE functions, so I assume these are intrinsic. So how come we're falling over on these two?? The other OLE programs seem fine. What are we missing?

Cheers, M@

[img]http://www.vernonsystems.com/images/logo_main_ani.gif[/img]


At 17 AUG 2006 01:16AM Matthew Crozier wrote:

OK, I believe I've sorted this out. It appears you MUST use OleCallMethod as a function - ie use it in an expression. Interestingly, you don't seem to need to declare it as a function though.

Cheers, M@

[img]http://www.vernonsystems.com/images/logo_main_ani.gif[/img]


At 06 AUG 2007 01:25AM Matthew Crozier wrote:

It appears you MUST use OleCallMethod as a function - ie. use it in an expression.

And for completeness, it appears you MUST use OlePutProperty as an intrinsic subroutine, without a declaration or CALL statement. Otherwise you could get either B105 or SYS1000 errors.

I just thought I'd wait a year before saying that ;) - M@

[img]http://www.vernonsystems.com/images/logo_main_ani.gif[/img]

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/7d57cffc8feb8a6f852571cd00179803.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1