Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Events
Message
De
06/01/2014 17:00:18
 
 
À
06/01/2014 16:14:56
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Re: Events
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01591422
Message ID:
01591426
Vues:
113
This message has been marked as the solution to the initial question of the thread.
There should only be one READ EVENTS for your entire application. READ EVENTS does not say stop program execution. It says, "Start looking for events". If you want the program to stop, you need a modal form.


>Hi All:
>
>My top-level program calls a menu.
>
>
>SET MESSAGE TO 'Setting up Files...'
>DO SetUpFiles WITH _screen.oStuff.lTest, _screen.oStuff
>SET MESSAGE TO ''
>
>llMenu = .t.
>PUSH MENU _msysmenu
>DO pm.mpr
>READ events
>
>do cleanup
>quit
>
>
>In the menu, one option calls a program - 'do foo'.
>
>In foo.prg:
>
>
>DO GenEmailFile WITH toStuff
>
>SELECT * ;
>	FROM TempMail ;
>	WHERE !EMPTY(tm_body) ;
>	INTO CURSOR curEmails
>
>DO FORM emaillst2
>READ events
>Messagebox('PROCESS COMPLETE!')
>
>
>Why does it display the messagebox before I exit from the form! And it makes no difference whether I have the READ EVENTS after the DO FORM or not!!
>
>Thanks,
>
>Yossi
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform