Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
NODEFAULT, DODEFAULT, etc
Message
De
04/04/2004 19:25:25
 
 
À
Tous
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Titre:
NODEFAULT, DODEFAULT, etc
Divers
Thread ID:
00892136
Message ID:
00892136
Vues:
51
I know that different questions have been posted on how to keep code from firing in certain events (e.g. in a form.closing, setting Exception e.true, etc.) My question is along the same lines, but different situation.

Let's say I have a base form class (frmBase), with code in the LOAD event. I then use that form to create a 2nd form (frmOrders). In frmorders, I also place code in the LOAD event. I think the LOAD code for frmOrders will run, and then the LOAD code in frmBase will run.

In that instance, it's OK, because I'd want that to happen - though it's certainly different than in VFP, where the code in frmBase would only run if I put a DODEFAULT in frmOrders.

However, there may be specific instances where I wouldn't want the code in frmBase to run (or maybe txtBase or another control). In that instance, how can I 'stop' the code from running? Only thing I've been able to come up with is to set a global flag to true in the inherited control, and check back in the base form/control to see if that flag is true or not before executing the code.

Any ideas?

Thanks,
Kevin
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform