On Mar 25, 3:06 pm, John W. Vinson
<jvinson@STOP_SPAM.WysardOfInfo.com> wrote:
> >Simply:
> >When my form opens, it should cause a popup; the user selects a value,
[quoted text clipped - 22 lines]
>
> John W. Vinson [MVP]
John -
TX SO much for your reply...
I never knew about the window mode property... 1 of the little things
that slipped by I guess :)
This is EXACTLY what I want - to be able to suspend code execution !!
(I wonder - is there a way to do this without using a form's window
mode? ie: could I stop code execution until an event trigers
continuation ? )
I am curious though -
Even when I use the dialog window mode in the form's on open; I notice
that a control box which is equal to a user function (ie: text box
source = fGetMyValue() ) is still executed PRIOR to completion of
the on open code.
Now - this is easily worked around by un-binding the control, and
assigning it in the on open code - so it's not really a big problem.
BUT - one would certainly expect that the acdialog which halts code
execution would prevent the control's code from being executed in
addition to any other code.
TX again, John!
Bob
bobg.hahc@gmail.com - 26 Mar 2008 15:56 GMT
On Mar 26, 9:47 am, bobg.h...@gmail.com wrote:
> Even when I use the dialog window mode in the form's on open; I notice
> that a control box which is equal to a user function (ie: text box
[quoted text clipped - 9 lines]
> TX again, John!
> Bob
Adden:
I've now done just what I described; but the field's value is not
displayed correctly - even after a "me.refresh".
Is there something special I have to do to get a field to display it's
correct CURRENT value?
TIA (again :)
Bob
John W. Vinson - 26 Mar 2008 18:13 GMT
>Adden:
>I've now done just what I described; but the field's value is not
>displayed correctly - even after a "me.refresh".
>
>Is there something special I have to do to get a field to display it's
>correct CURRENT value?
Shouldn't. Please post your code, and the names and control sources of the
relevant form controls.

Signature
John W. Vinson [MVP]
John W. Vinson - 26 Mar 2008 18:12 GMT
>I am curious though -
>Even when I use the dialog window mode in the form's on open; I notice
[quoted text clipped - 7 lines]
>execution would prevent the control's code from being executed in
>addition to any other code.
It suspends the code in the *CALLING* form's module; any code in the *CALLED*
form will of course execute as normal. Maybe you need to use the form's Load
event, which executes after the connection to the recordsource has been made.

Signature
John W. Vinson [MVP]