Heenan, Lambert
Lambert.Heenan at aig.com
Wed Sep 1 12:04:09 CDT 2004
If you want to be *sure* that the timer event will not fire again then set the timer interval to zero. > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [SMTP:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia > Sent: Wednesday, September 01, 2004 12:29 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Prompt after Form loads > > On Timmer w/ a static variable is what I ended up using (plus after it > fires I shoot the timer interval to 2hrs (more than enough time) so > it hopefully won't fire again until after their session is done. > > On Wed, 1 Sep 2004 08:41:20 -0700, Francisco Tapia <fhtapia at gmail.com> > wrote: > > Just tried it and the OnCurrent event also fires before the form is > > loaded :(, gonna try the OnTimmer... > > > > > > > > On Wed, 1 Sep 2004 08:35:54 -0700, Francisco Tapia <fhtapia at gmail.com> > wrote: > > > I will try this option Gustav, thanks :D. > > > > > > btw, Rocky... What I meant by autoload was that in the Form_Load event > > > I have code that loads data to the form. because it was in the > > > form_load event, the prompt was occuring before the user had a chance > > > to see the form. > > > > > > On Wed, 1 Sep 2004 12:34:56 +0200, Gustav Brock <gustav at cactus.dk> > wrote: > > > > Hi Andy and Francisco > > > > > > > > I would suggest OnCurrent. > > > > To prevent multiple prompts, set a static flag: > > > > > > > > Static booIsPrompted As Boolean > > > > > > > > If booIsPrompted = False Then > > > > ' Ask if you user wish to load data. > > > > <code> > > > > booIsPrompted = True > > > > End If > > > > > > -- > > > -Francisco > > > > > > > > > -- > > -Francisco > > > > > -- > -Francisco > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com