Going back to your original requirement, the question is how you can be selective on what to run during development mode?
In essence, there are two options:
1. External control, such as that suggested by vbaInet
2. Internal control, which is selective and tiggered by someting straight-forward.
Option 1 is complicated and involves other applications and/or services and probably falls in the "too hard" basket for your requirement.
Option 2 seems much more attainable and is easily in your control (given that you are developing the DB).
My approach would be to have a form which loads automatically when the DB opens and check the presence of a table, or a flag within a table. My own solution is to use a menu table which has a series of start-up flags and values which determine behaviour (akin to the Switchboard Manager). One such flag might be a debug code which you can set and which detemines whether to display your reminder or to go to the normal main page. This flag could remain a permanent feature of your DB, so you can set it when you need it for debug purposes.
On balance, I'd stick with the KISS principle and stay within the boundaries of Access to control your startup.
Apologies if this sounds like teaching you to suck eggs, Grandma.
