Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Button calls a form, form returns values, button code co
Message
 
 
À
29/08/2008 09:22:55
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 9 SP2
Divers
Thread ID:
01342942
Message ID:
01343080
Vues:
17
I used the same method as Rob more often than another one, but I agree with Tamar's reasoning. Using extra object will separate these two forms from each other.

>Ok, yours and Christoph's ideas are good. How should I choose? Is there an advantage of one over the other or is it just personal choice?
>
>>The way I like to handle this is to put those properties an the original form, and populate them from the second form. When you launch the second form, in the load, make an object reference to the first form using something like
>>
>>THIS.oCalledFrom=_SCREEN.ACTIVEFORM
>>
If it's not broken, fix it until it is.


My Blog
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform