J
Jim Tinder
I have downloaded and reviewed the SEQFAQ article from the
knowledge DB. It provides some code to disable the shift
key bypass of the autoexec procedure. However it is not
clear if this will put me into a catch-22 situation.
I have written a number of DB's; but, all till now I
haven't been concerned about the bypassing of the autoexec.
My DB's have an autoexec that opens a form that acts as a
main menu. The close macro of this form exits the
application (Access).
It appear the procedure outlined the MS article set the
disable at the DB level (?) If so if I set it in my DB's
how will I be able to enter design mode if it automatically
opens the main menu and the exit closes Access?
Is there a way to do a "selective"/"exclusion" bypass?
Thanks
Jim
knowledge DB. It provides some code to disable the shift
key bypass of the autoexec procedure. However it is not
clear if this will put me into a catch-22 situation.
I have written a number of DB's; but, all till now I
haven't been concerned about the bypassing of the autoexec.
My DB's have an autoexec that opens a form that acts as a
main menu. The close macro of this form exits the
application (Access).
It appear the procedure outlined the MS article set the
disable at the DB level (?) If so if I set it in my DB's
how will I be able to enter design mode if it automatically
opens the main menu and the exit closes Access?
Is there a way to do a "selective"/"exclusion" bypass?
Thanks
Jim