Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Tip of the Day - a Way To Avoig Dangling Object Referenc
Message
From
05/11/1999 17:21:18
 
General information
Forum:
Visual FoxPro
Category:
Object Oriented Programming
Miscellaneous
Thread ID:
00287529
Message ID:
00287840
Views:
24
>>>>In the access method I do the following.
>>>>
>>>>RETURN EVAL( "THISFORM.List1" )
>>>>
>>>>Now in the command button'c click event I have the following code:
>>>>
>>>>=MESSAGEBOX( THISFORM.poList.Name )
>>>>
>>>>Does this idea fall into the scheme of what you are doing, trying not to leave any dangling object references?
>>>
>>>I don't see here what NULLs the object reference in THISFORM.poList property
>>>In my case now it is a local variable which exists only when the method works.
>>>
>>>Nick
>>
>>
>>To be honest, I don't know how this works. But what if the object reference is never stored in poList because every time you access, you're returning EVAL( "THISFORM.List1" ). If that's the case, you won't need to set poList to NULL because it never really had an object reference.
>
>If it is not stored, there should be no worries. :) Then you don't need poList property at all.

That may very well be true. That was why I was wondering if doing the above would fit into the scheme of what you are doing. It looks like you're saying it does not. :)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform