General information
Category:
COM, DCOM and OLE automation
Try
loObject = Null
Release loObject
The first line (loObject = Null) may be unnecessary, but XL does funny things sometime, so I've made myself get used to using both lines.
Alan
>HI
>In a program I create an instance of registered COM object, and assign a reference to the local variable.
>loObject = CREATEOBJECT(“Component.ComponentClass”)
>After the program is finished VFP still keep instance of the COM object in a memory. So next time I run my program it uses previously created object, instead of creating new one.
>What should be done to avoid this behavior?
>
>TIA
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only