Access 2010 Opens and Bypasses Startup Options

I have an Access 2010 database that is split with the front end on the local PC which links to the back end on the network.

Under File, Options, Current Database, the Display form is set to open frmMain.

This works perfectly 99% of the time, but I have an intermittent issue where my users do something to get kicked out of the database or they closed out and open the database back up and it opens without opening frmMain.  It basically opens bypassing all the startup options, and the only fix is to reboot the PC which drops a new copy of the front end on the PC.

Any idea how to stop this from happening or to correct without having to drop a fresh copy of the front end on the PC?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey CoachmanMIS LiasonCommented:
Guess here.

When the user closes the db in an unpredictable way, the "locking" file may be left open.
This file is create by Access when the db opens.
You have to delete this file manualy, if it is not closed when the db is closed normally.

Other Questions..
Is this DB properly "Split"
(Each user has there own copy of the front end (forms, reports), ...and the backend (tables) are stored on a share on the network?)
Senniger1Author Commented:
I've deleted the file locking file (e.g. .laccdb) when this happens and it doesn't make a difference.

Yes, the db is split properly.  Each user has their own copy of the front end and the backend is on a network share.
Jeffrey CoachmanMIS LiasonCommented:
Not sure then...
I know that if you open the db while holding down the Shift key, the startup options will be bypassed...

Perhaps you could tell us a bit more about this:
intermittent issue where my users do something to get kicked out of the database

This might happen if they try to re-open the db *immediately* after closing it (not enough time for Access to close the lock file)
Other than that, ...lets see if another Expert has any experience with this particular issue.

Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Dale FyeOwner, Developing Solutions LLCCommented:
Your guess is as good as mine Jeff.  I've been monitoring to see if anybody came up with anything, because I was stumped.

Jeffrey CoachmanMIS LiasonCommented:

Then try the usual:
Compact/repair, ...then retest for the issue.
If the problem still persists...
Create a new reference front end, and copy all of the existing objects to this new db and redistribute...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I'd also try a Decompile, just before you create the new FE as suggested by Jeff. To do that, create a shortcut with this as the target:

"full path to msaccess.exe" "Full path to your db" /decompile

Run that, then open the VBA Editor and click Debug - Compile. Fix any errors, and continue doing this until the Compile menuitem is disabled.

Now create the new FE and copy everything over (and make sure to compile in that new FE).
Senniger1Author Commented:
Regarding "intermittent issue where my users do something to get kicked out of the database", I can't say for sure since my users don't really know what happened.  I know some have opened immediately after closing and it makes sense they'd get the file lock.

What doesn't make sense is even if there is a file lock and you delete it, you should then be able to open it and see the main menu.  When this happens, it's almost like the db is corrupt because the main menu won't open.  I haven't tried to just manually open it once it's in this state, but I'll try that the next time.

I do compact the db often.  I did neglect to mention the local copy is a .accde file
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Are you certain the workstations are fully up to date in regard to Access/Office and Windows?

Are you deploying the .accde file from an environment that is the same version as your users? For example, if your users are running 2007, you should be doing your final compile/deploy in 2007, and not 2010 or 2013.

Are you using any non-native controls, including any from Microsoft? There are very, very very few compliant ActiveX controls for 2007, and all of them are from 3rd party vendors.
Senniger1Author Commented:
The PCs are all up to date and use the same image.  Yes I'm deploying the .accde file from an environment which is the same as my users.  I don't think I'm running any non-native controls.

Note this issue doesn't happen often, I'm just trying to figure out what is going on.

Thanks much!
Jeffrey CoachmanMIS LiasonCommented:
I'm stumped...
Perhaps its the main form itself...

As a quick test, ...try creating a new, test, simple "Main Form"
...and see how that goes...

But I hate just guessing...
I'll step aside now and let you work to conclusion with Scott.

Senniger1Author Commented:
Thanks Jeff, I really appreciate your time.  Another big obstacle is it's intermittent and not all my users report when it happens so I don't really have a handle on how often it occurs.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Was the database created in 2010, or was it upgraded to 2010? We've had reports of odd behavior with databases that were upgraded from .mdb files (and even ones that were upgraded from early versions of .accdb files).

If so, then it might be prudent to create a new, blank .accdb file in the relevant version, and import everything into that new database file. Of course, this assumes you haven't already done so.

Other than that, I'm stumped.
Senniger1Author Commented:
It was created with 2010.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Gotta be environmental, then, and that could entail a LOT of things.

Since the "copy a new FE" method works, then something to consider might be to create a "launcher" sort of application, which basically copies over a new FE from a public resource, and then launches that local copy. This could be as simple as a batch file with a few lines, to a .NET app, to a commercial product.

I've had success with the batch file method:

@echo off
XCOPY "\\NetworkPath\Install\YourFE.accde" "c:\Local Folder\YourFE.accde" /y /q
START "c:\Local Folder\YourFE.accde"

The copy takes a second or so, but in most cases users are okay with that. I've also created launchers with .NET for situations that required a bit more robust management (like password protection, etc).
Senniger1Author Commented:
I appreciate everyone's input and have been working with all the suggestions.  So far, the issue hasn't reappeared, however, I'm not sure if it's correct or what would have corrected it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.