Andy Lacey
andy at minstersystems.co.uk
Tue Oct 28 05:07:43 CST 2003
Hi Stuart. Exactly William's thought. Blimey we could have a consensus here. -- Andy Lacey http://www.minstersystems.co.uk --------- Original Message -------- From: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Subject: Re: [AccessD] Disabling the user Date: 28/10/03 01:48 On 28 Oct 2003 at 11:24, Andy Lacey wrote: > Hi folks > If you want a routine (called from a command button) to finish before the > user can do anything else in the app how would you achieve that, short of > putting up a message saying "Wait" and cutting their fingers off if they > don't? The forms quite busy and there are a number of buttons they could > press, or close the form etc, and I could write a function which just > disabled all of those things then re-enabled them when the routine's > finished, but it's a bit messy. Is there a cleaner way of just temporarily > disabling the app? > -- One way would be to open another form modally ie. "WindowMode=acDialog" with no buttons or ControlBox and put the routine in that form's OnOpen. Then close the form when it has finished. -- Lexacorp Ltd http://www.lexacorp.com.pg Information Technology Consultancy, Software Development,System Support. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com ________________________________________________ Message sent using UebiMiau 2.7.2