Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SYS(3095,oObject) has a bug
Message
 
 
To
28/11/2005 16:20:54
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows 2000 SP4
Network:
Windows 2000 Pro
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01072326
Message ID:
01072613
Views:
16
Hi Christian,

The following works in my test
DEFINE CLASS oTestCom AS Custom OlePublic
  FUNCTION SysTest(toObj) AS Integer
    RETURN SYS(3095, toObj)
  ENDFUNC
ENDDEFINE
...
loObj = CREATEOBJECT("mydll.oTestCom")
? SYS(3095,loObj), loObj.SysTest(loObj)  && Dispalys the same pointer twice
>
>this doesn't work either, but thx for particiopating anyway.
>
>I think we can stop this discussion here since it just doesn't work.
>
>So if one wants to use SYS(3095) from inside a COM object to get the IDispatch pointer of the same object, just forget it or wait for a fix from MS.
>
>As a workaround one has to call SYS(3095) from outside the COM class.
--sb--
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform