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?