[AccessD] Disabling the user

Thanks John. Yes I think that's where I'm heading (option 2). Am going
to take a look at JC's progress form as a basis.

Andy Lacey
http://www.minstersystems.co.uk 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
> Sent: 28 October 2003 16:14
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Disabling the user
> 
> 
> Hi Andy,
> Similar to Stuart's suggestion, I've handled this situation using two
> methods:
> 
> -Present a progress/info form with a timer set to the maximum 
> amount of time this process will take which I only use for 
> non-critical processes to give the user a heads up to what is 
> happening.
> 
> -Open a modal pop-up form with info/progress that then calls 
> the procedure. When the procedure returns a value close the 
> form. The command button doesn't actually call the procedure 
> but rather it calls the form that calls the procedure, thus 
> making the procedure calling form easily reusable, just have 
> a button that opens the form.
> 
> It sounds like the latter might fit your case.
> 
> HTH
> John Bartow
> 
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart 
> > McLachlan
> > Sent: Tuesday, October 28, 2003 5:46 AM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Disabling the user
> >
> >
> > 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
> >
> >
> 
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/a> ccessd
> Website: 
> http://www.databaseadvisors.com
> 
>