Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Instantiate form class
Message
From
08/11/2000 22:23:45
 
 
To
08/11/2000 17:42:39
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00439181
Message ID:
00439526
Views:
17
>The following is a translation of my previous reply to Rodrigo:
>
>Rodrigo:
>
>As Ed Rauh correctly says, public variables are a bad idea.
>To answer your question, yes you do need a CLEAR EVENTS.
>

There is an alternative - a modal form provides its own wait state; it runs until it terminates, and then the code picks up from the next line of code following the DO FORM or oForm.Show(1)

>The most normal way of doing this, is that your project should have a common man point of entry in a prg (ie. main.prg). This prg instances the main menu and then issues a READ EVENTS. The menu is now functionaland from there you can open all your forms.
>
>When you end the program, for example with a main menu exit option that issues a CLEAR EVENTS, control returns to main.prg at the point immediately after READ EVENTS.
>
>There you clean up and close.
>
>I also recommend you visit the Spanish newsgroups at microsoft.public.es.vfoxpro where there is a lot of Spanish speaking VFP users. I also want to mention that there will be a chat here in the UT, in Spanish, on Wednesday December 13th at 9:00 pm Buenos Aires time (see: http://fox.wikis.com/wc.dll?Wiki~IntroducciónAOrientaciónDeObjetosEnVFP)
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform