Greetings to the well of knowledge...
Have read every other posting on this particular error message but have not found my particular circumstance.
It's an Access 2010 front-end using an SQL Server DB using ODBC.
The users reporting this error successfully opened the database at some point during the day, then exited. Later in the day, when they try launching the database again, this error occurs and shuts down the front-end. The workaround has been for the user to logoff from Windows and log back on at which point the user can again open the front-end.
I am baffled as it random and does not happen all the time. It's as if the last time Access was shut down, it didn't shut down cleanly and left something behind (no, no lock file left behind).
The startup code in the DB just launches a form with push buttons to select various functions, no tables/queries are opened at this point, but a timer is started so that when the front-end has been idle for 20 minutes, it shuts down automatically. I have not been told that this is the particular circumstance that triggers the error.
Any thoughts?
Regards,
Ken
Have read every other posting on this particular error message but have not found my particular circumstance.
It's an Access 2010 front-end using an SQL Server DB using ODBC.
The users reporting this error successfully opened the database at some point during the day, then exited. Later in the day, when they try launching the database again, this error occurs and shuts down the front-end. The workaround has been for the user to logoff from Windows and log back on at which point the user can again open the front-end.
I am baffled as it random and does not happen all the time. It's as if the last time Access was shut down, it didn't shut down cleanly and left something behind (no, no lock file left behind).
The startup code in the DB just launches a form with push buttons to select various functions, no tables/queries are opened at this point, but a timer is started so that when the front-end has been idle for 20 minutes, it shuts down automatically. I have not been told that this is the particular circumstance that triggers the error.
Any thoughts?
Regards,
Ken