I have a database that is used by an entire department, daily. Recently, it has started crashing on startup. Not always, sometimes more than others, but it is getting steadily worse, seemingly as the entire department migrated to Windows 10 and Office 365. My lastest build seems to have fixed the sporadic nature - it now crashes very reliably.
It has been repeatedly decompiled, compact and repaired - no help. There is no code that is throwing errors, or deliberately closing anything. In fact, the database often opens nicely, splashes the start-up screen, closes that and goes to the main screen, where it sits for a few seconds, doing absolutely nothing - just waiting for the use to make a move. The VBA window confirms that nothing is running. Then, for no reason that I can see, with NO action from the user, not doing ANYTHING else on the machine, Access just quits.
It seems that if I 'catch' it quickly enough, by clicking on a button or in a text window, I can prevent it from quitting. Once it gets started doing something, this never happens - the app runs very nicely. But this crash on start-up is getting to be a problem, and I am at a loss as to what to even look at. It is difficult to debug code when there is no code running.
Can anyone suggest something I might try?