Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Releasing memory for ActiveX properties
Message
 
 
To
11/02/2002 19:53:56
General information
Forum:
Visual FoxPro
Category:
ActiveX controls in VFP
Miscellaneous
Thread ID:
00618633
Message ID:
00618676
Views:
13
This message has been marked as the solution to the initial question of the thread.
Assigning o = null releases reference to the word object and the release o command releases variable o and indirectly releases reference to the word object.
It's recomended to explicitly release reference to an object by assigning null to the variable. See http://fox.wikis.com/wc.dll?Wiki~ManualGarbageCollection~VFP on garbage collection in VFP .
To release world instance you have to use o.quit.

>Not sure. It raises the other question how to release an instance of Automation Server.
>o = CreateObject("Word.Application")
>o = null
>&& or
>release o
>
>doesn't help and WinWord still in processes on my NT box , which makes me think
>
Node.Data = Null
>won't help and I can't see any way to check it out.
>
>
>
>>I think the VFP equivalent would be
Node.Data = Null
>>
>>>I've got the following extract from the doc.
>>>
>>>Node.Data =
>>>
>>>Note: You should free memory owned by Data property on deleting Node, use for these purposes OnDeletion event handler and set Data to Nothing.
>>>
>>>in VB
>>>Node.Data = Nothing
>>>
>>>
>>>How can I free memory for that in VFP ?
>>>
>>>Thank you.
>>>Michael
--sb--
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform