Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Releasing internal object references.
Message
From
06/10/1998 13:13:29
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Releasing internal object references.
Miscellaneous
Thread ID:
00144275
Message ID:
00144275
Views:
55
I think I know the answer to this, but just in case there is a strategy I don't know about...
In the past when I have an object on a form that holds a reference to another form object, I have just set o1.oRef = .NULL. in the form.destroy. This has been fine because this design was happening at the form level.
I am now trying to create a class that has to hold a reference to another object on the form, and I would like for the class to watch out for itself. I quickly found that THIS.oRef = .NULL. in the object's destroy event won't do the trick. Is there another way to make this class self sufficient? IOW, I don't want to have to rely on form code to release the object.
Erik Moore
Clientelligence
Next
Reply
Map
View

Click here to load this message in the networking platform