Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Close executalbe
Message
From
21/03/2006 16:59:26
 
 
To
21/03/2006 07:33:56
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01105072
Message ID:
01106419
Views:
27
>>I am setting up an object property to NULL and it's not releasing the server.
>
>The problem may be either on client or on server side.
>If the server is released after unloading client application or after RELEASE ALL or CLEAR ALL on client side then the problem is on client side.
>Multiple references to server interface(-s) usually cause this.
>
>Otherwise, if the server is not released even after client unload then the problem is on a server side. Once again multiple references to server object (-s) in the server application may do so. For example storing server object reference in public variable or property on the server side supress server release.
>
>If the problem is on a server side then try to instantiate it as a local object in VFP session and play with it.
>Put some messagebox or wait command to Destroy method to ensure that object is really destroyed. Type in the command window to create local server object:
>
oTest = NEWOBJECT("YourServerClass", "YourServerClassLib")
>Then type:
>
oTest = Null
>to relase it.
>
>If it releases properly then there is no problem with object initialization. You need to play with calling methods and setting properties for to recognize after which code it does not releases.
>
>Hope this helps.
>
oTest = Null
from the command line releases remote object. So it does from the program but not every time.
Previous
Reply
Map
View

Click here to load this message in the networking platform