Francisco Tapia
fhtapia at gmail.com
Sat Sep 4 11:08:30 CDT 2004
I will try this solution later... thanks :D On Thu, 2 Sep 2004 10:35:14 +0200, Gustav Brock <gustav at cactus.dk> wrote: > Hi Francisco > > > I tried the counter solution, and it fires before the form is "visible" > > You are right, missed that, but here is how to do this without the > Timer: > > First, create this function in the subform: > > Private Function ShowAtOpen() > > Static booOpened As Boolean > > If booOpened = False Then > ' Replace with your code. > MsgBox "Load?", vbQuestion, "Francisco" > ' Run only once. > booOpened = True > End If > > End Function > > Now, create a textbox in the subform, make it not Visible, and bind it > like this: > > =ShowAtOpen() > > This will pop the code when the form and the sub have been rendered > including controls bound to the recordsource of the form. The only > limitation I can see is, that other controls bound to an expression > (=something()) may have their values retrieved after the firing of > ShowAtOpen. > > /gustav > > > > On Wed, 1 Sep 2004 20:53:36 +0200, Gustav Brock <gustav at cactus.dk> wrote: > >> Hi Francisco > >> > >> > Agreed, I use them as a very last solution. They do CAUSE flickers, > >> > and they interrupt other process as well. Such as adverse behavoirs > >> > when using a combo bx and you find that your dropdown doesn't stay > >> > dropped, because the timer continues to fire off in the background :D > >> > >> Except in this case ... did you try the counter solution? > >> Works excellent here. > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- -Francisco