Hlp Plse 'Jet database engine stopped'

  • Thread starter Thread starter Junior
  • Start date Start date
J

Junior

Running Acc2K, WinXP, also have AccXP installed on same PC
Yesterday, I upgraded with latest Office XP SP and WinXP SP

Now , when i try to open a select query in a DB Acc2k i get error pop up.
"The MicroSoft Jet Database engine stopped the process because you and
another user are attempting to change the same data at the same time."
I am the only user .
All the querys in this DB worked fine last week - Now, some querys work and
some produce this error message.
Didn't find any help in the KB. Help please
 
With Access closed, navigate to the folder that your database is stored in. Do you see a
file with the same name as your database, but with an .LDB (Locking Database File) file
extension? Note: you may not see any file extensions, depending on your Windows settings,
but you should still see an indication of Locking Database File, if indeed you have a .LDB
file present. If you find this file (typically 1 KB in size) and your database is not
open, then delete it.

See Introduction to .ldb Files
http://support.microsoft.com/default.aspx?scid=kb;en-us;208778

Tom Wickerath
Bellevue, WA. USA
_____________________________________________


Running Acc2K, WinXP, also have AccXP installed on same PC
Yesterday, I upgraded with latest Office XP SP and WinXP SP

Now , when i try to open a select query in a DB Acc2k i get error pop up.
"The MicroSoft Jet Database engine stopped the process because you and
another user are attempting to change the same data at the same time."
I am the only user .
All the querys in this DB worked fine last week - Now, some querys work and
some produce this error message.
Didn't find any help in the KB. Help please
 
Tom Thanks - I had already tried that - no extra ldb
I think I figured out what was going on.

I use a secure MDW for some of my DBs.
they start out as an mdb and later create a secure version
using a different MDW.

while logged on into a secure mdb as database owner , I had opened
the other non secured DB and made some changes.
Later, when i opened the nonsecured DB using the system mdw i experienced
the problems i described.



an interesting
 
Back
Top