Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Difference between forms and class based forms?
Message
From
24/03/2009 23:32:30
 
 
To
24/03/2009 22:57:30
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01391221
Message ID:
01391283
Views:
111
I still don't get it ... that is, I understand your explanation, but have no inkling why it would explain why I would live happily if I no longer use SCX.

Removing two "unneeded" files doesn't mean very much to me, certainly not imparting any happiness.

Isn't there some other benefit? Clearly, VCX based forms are common, maybe even, for all I know, the standard. I would assume some advantage beyond merely saving a couple of files.

Cheers,

Jim



>>Fair enough. Why? What difference does it make?
>
>First off, class-based forms don't have a dataenvironment object (it's null, I guess - never checked). You can add it after instantiation (I guess again, never tried that). If you have your own way to open the tables for your forms, then you just make sure that code runs from form's .load() and you're done. In a .scx, there's usually some pathing info stored in the DE, code that you don't see immediately (as the DE is a separate object, not really a part of the form, just saved with it, but you don't see it in the PEM window until you specifically rightclick on no particular control and select DE from there, but then you don't see the form).
>
>Also, if you already have a form class, then instantiating just one form off that class is just adding two unneeded files to your project. If you can, or prefer to, manage without a DE, forget scx and live happily.
Jim Nelson
Newbury Park, CA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform