Stuart McLachlan
stuart at lexacorp.com.pg
Wed Oct 6 17:12:19 CDT 2010
First thing I'd do is wrap the event code in Docmd.Hourglass True ... Docmd.Hourglass False to discourage them from clicking. If that is not enough, I'd have a sub which steps through all the controls on the form and either enables or disables them based on a parameter. Then wrap the long running code in two calls to that function. -- Stuart On 6 Oct 2010 at 16:53, Debbie wrote: > I have a form in access 2007 that has a lot of code that runs when > certain events happen. These take several seconds to complete and > occasionally if a user changes thier mind or gets impatient and clicks > elsewhere before the code finishes I get errors and problems. > > For example: I have an option box that shows or hides various > subforms. Click between then quickly and before too long you will get > stuck on one option and can't change it without changing something > else in the form then going back. > > Still doing my best to educate fast clicking out of them, especially > on this form, but ideally I need some way to keep new entry from > happening while code is running. I have just experimented with an > inconspicuous modal form that opens on code firing and closes when it > is done, but still get the option button sticking. Either I need a > different solution, or the problem is not what I think it is. Anyone > have any ideas? > > Debbie > > Sent from my iPhone > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >