Cannot open database - non-existent multiple users

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am getting a message when I try to open an Access database (Access 2000):

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

What could be causing this, when there is only one user accessing the database? Is there any way to recover from this? I have tried copying the file, but the copy gives the same response (which is clearly incorrect since the copy could not possibly be being accessed by anyone else). There is no security on the database, so I am not sure this is the right Group.

This has been happening a few times in the last few weeks - after several years of trouble free performance (starting life as an Access 95 database). Perhaps it is time to move to SQL Server ...

Thanks in advance
 
This particular message is rather cryptic ... in the situation you describe,
it usually indicates a corrupt database and has nothing to do with multiple
users. Check Tony Toews site for further info and possible fixes:

http://www.granite.ab.ca/access/corruptmdbsymptoms.htm

--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP
Les Russell said:
I am getting a message when I try to open an Access database (Access 2000):

"The Microsoft Jet Database engine stopped the process because you and
another user are attempting to change the same data at the same time."
What could be causing this, when there is only one user accessing the
database? Is there any way to recover from this? I have tried copying the
file, but the copy gives the same response (which is clearly incorrect since
the copy could not possibly be being accessed by anyone else). There is no
security on the database, so I am not sure this is the right Group.
This has been happening a few times in the last few weeks - after several
years of trouble free performance (starting life as an Access 95 database).
Perhaps it is time to move to SQL Server ...
 
Back
Top