Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Object as form property
Message
From
05/10/2007 12:01:57
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
05/10/2007 09:26:17
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 8 SP1
Miscellaneous
Thread ID:
01258596
Message ID:
01258972
Views:
13
>>While the other advice you've been given is correct, unless there's a good reason, I'd add the property in the Form Designer and just assign it in Init.
>>
>>Tamar
>
>What would drive the decision to do it one way or another?

It being allowed/possible or not would influence it :).

Also, if the property is added at design time, it will pop up in the intellisense which would at least help you keep the spelling consistent. Also, if your code happens to fire in a wrong order (i.e. reference this object before it's instantiated), you'd get a different kind of error message :). That is, instead of "PEM not found" you'd get "is not an object". Third, if you add it at design time, then it can have _access and _assign methods - the former being a perfect place to instantiate it on demand.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Reply
Map
View

Click here to load this message in the networking platform