Stuart McLachlan
stuart at lexacorp.com.pg
Mon Dec 5 15:55:15 CST 2011
Presumably when you say "dangerous to use", you are referring to triggering control events on the form. What happens if you: 1. build a function which checks for the condition and closes the form if necesary 2. Call the function as the first step in any potentially dangerous control event. -- Stuart On 5 Dec 2011 at 16:09, Benson, William (GE Global Re wrote: > There is something that I require to be true, upon testing, or this one > particular form I consider to be dangerous to use. It is a condition > that may change over the session, it is not necessarily a stable > condition during the user session. > > I understand it can be tested for on Form Open, and the opening of the > form can then be canceled. But how about afterwards: For example, > suppose on activation of the form, I want to test the condition again. > According to an error message I just got, I am not allowed to close the > form during the form's events. > > I am kinda stumped how to protect myself now, if I cannot make this > check-environment-and-dismiss-form occur on a form's events. > > I guess I could have a hidden form checking this on a timed basis but I > am sure that will cause some regrets. > > TIA... > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >