Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Controlsource creates public variable
Message
From
19/02/2001 10:46:17
 
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00477295
Message ID:
00477300
Views:
32
Hi!

No, it is not normal because it takes memory. Try to put 'Release this' command in the destroy event of the form.

>>Hi!
>>
>>I guess it is by design.
>>Anyway, this 'leftover' is from the incorrect ControlSource specifying withoy alias name. Just a field name without alias oftenly cause the same problem.
>>
>>>If I put an undefined variable in the controlsource of a textbox, FoxPro automatically defines the variable as Public. Is this normal behavior? I know, I shouldn't be doing this, but I'm dealing with leftovers from someone else that was using public variables. I'll fix it by taking the variables out of the controlsource, but was just curious that this was happening.
>
>Something else I just noticed, is that when I run a form from the command window and then close it, an object reference to the form remains in memory. It's an empty reference with no properties, but it is still there. Is this normal as well? Thanks.
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.com
ICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs

It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform