Got the following message when I opened a database front end I'm working on.
There are no other users involved (stand alone PC).

"The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time."

:confused:

Pointers please to get out of this.

Is it an MDB file? Do you get the same results when you open while holding down a <SHIFT> key?

Yep MDB and yep same when holding down shift key.

Hmmm....
That does not sound right. Nothing should be executing when you hold down the shift key. Did you turn off the AllowByPassKey? You might try a /decompile (http://www.granite.ab.ca/access/decompile.htm) and see if that corrects the problem.

AllowByPassKey is on.

Tried the decompile with the following batch file:-

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE""C:\Documents and Settings\SDawson\My Documents\ACCESS\Production\production_new.mdb" /decompile

pause

Still no joy. Same message.

Plan B?

Suggested plan B (http://allenbrowne.com/ser-47.html)

Now I know what backups are for!!!!

Thanks for trying.

You're welcome. Try Allen's suggestions. They still might work.

sometimes you can get stuck processes - does rebooting the pc help.

if not, perhaps you have locked a table or done something else with some startup code.

gemma, rebooting not the answer.
Your comments re locked tables or startup code may prove to be correct if only I could get into it to find out! It was a new form I was working on the last time it was open.

Thanks

Just ran the utility JetComp.exe in:-

http://www.everythingaccess.com/tutorials.asp?ID=Access-Database-Corruption-Repair-Guide#3

It created an new database that I am able to open but the query and the form I was working on when I was last in have disappeared!

Still at least I can get in and the query and form were only a days work. Doh.
:)

I had this same problem with one of my databsaes and it was down to a a .ldb file. I tried to delete this file and it wouldnt go until the next day, so I moved my db into a new file and it worked fine.