Access 2003 MDB Startup Form Causes Crash

[AndrewMastKY]

I'm using Windows 8, but had the same problem occur in XP with Access 2003. MDB is located on a 2008 Server with HyperV.

For the past month I have been struggling to resolve this issue or even find the cause of it and just can't figure it out.

I have a 400mb MDB that contains mostly all linked tables to another MDB and SQL server and a boat-load of forms & reports.

I've been regularly modifying VBA code and it seems that after a good deal of code changes in various modules, I'll exit the application and attempt to reopen it and I get either "access has stopped working" error or "There was a problem sending the command to the program." or one of those errors. However, IF I hold the shift key down, and launch it, it starts normally.

One would think "Look at your startup form", which I haven't touched, but ok, after bypassing startup by holding shift key, DB launches and appears normal, (except doesn't launch into my startup form). Then I manually launch the startup form, and all works normally???

I remove the form from the startup process, launch the MDB without holding the shift key and it works fine. (no startup form, DB window appears only)

Again, after a normal boot (with no startup form), I can call the startup form, and it runs!?

ADDITIONALLY, because I have been having this happen daily, I've been getting used to making copies, but I'm finding that 50% of the time, the copied MDB experiences the same problem? I can copy a good working version, and the copy will produce the same problem?

Has anyone see anything as crazy as this? Any ideas?

[zmbd]

Without the code it is a hard thing to help you with...

What I would suggest to you at this stage is:

Bypass the startup as you already have.
Open the code behind your startup form.
On the very first line follwing the sub ... () place the STOP
SAVE
Debug - Compile
Fix any errors the show-up. Compile after each fix. Note that you must comple after each fix as the debugger stops at the first error encountered.
SAVE
Close and reopen the database.
You should enter the debug state immediately.
[F8] thru your startup

Once: Pressing [F8] fairly fast.
Second time: fairly slow.

If you get thru this two times without fault, or if when you [F8] slowly thru the code all is well, then more than likely the code is calling something that is not initalized and the application level error handling isn't running yet either.

This is a hard one to trouble shoot even with the code.

Please post the code - remember to format it using the <CODE/> button in the toolbar.

[NeoPa]

Please also check out these instructions before posting. One of them may help to find the error.

Before Posting (VBA or SQL) Code.

[calpurnia]

Yes, I know this is an ancient thread, but I came across it after experiencing a similar problem, and thought it was worth sharing my solution in case anyone else comes looking. I basically just copied all the code behind the startup form into Notepad, deleted the code from the form itself, and then copied back in the version from Notepad. It seems to have done the trick, though I can't explain why.

[NeoPa]

Hi Calpurnia.

Responding positively to an old thread is no problem.

What you've done there is to cause Access to re-compile the code afresh. It has to junk any previously held compiled code for that form and that might have got corrupted or somehow out of step. So, repasting in all the code can often be helpful if you are in a similar situation.

PS. Though I haven't got to that point yet I've just started to read I Claudius by Rupert Graves, wherein Julius Caesar's 3rd wife Calpurnia makes an appearance. It seems a coincidence you posted today.