Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SYS(3095,oObject) has a bug
Message
From
28/11/2005 16:59:28
 
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:
01072626
Views:
20
Hello Sergey,
loObj = CREATEOBJECT("mydll.oTestCom")
? SYS(3095,loObj), loObj.SysTest(loObj)  && Dispalys the same pointer twice
yes it does, but it doesn't solve the real problem.

instead of calling SysTest() on the object one can call SYS(3095) directly with the same result. So we gained nothing with this approach.

The problem was to call SYS(3095) in the COM object itself without relying an any code the client has to call ( SYS(3095,THIS) somewhere in the COM object ).

Regards
Christian
Previous
Reply
Map
View

Click here to load this message in the networking platform