Jet database engine error on stand alone database?

[Guest]

I have an unusual problem that seems to be recurring on several of my
databases. I have created a stand alone database with multiple linked tables,
queries, forms, and reports...no macros or modules. My secretaries are using
the database to record staff absences (most very successfully). However some
have been receiving the following message when trying to access the database:

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

Keep in mind that this is a stand-alone database...not a network
application. I have tried to "Compact and Repair", but cannot access the
database at all (the same message appears). There doesn't seem to be a common
thread to any of the failing databases as far as user error or such. Some
have hundreds of records...others have just a few. I am at a loss; if you
have a clue as to why this might be happening or how to fix it, I would
appreciate the help.

 

[Joan Wild]

That message commonly comes up if someone exited the application in an
abnormal way (power button, ctrl-alt-del).

With the database closed, see if there is a file with the same name but an
ldb extension in the same folder as the mdb. If there is, delete it.

Then open the mdb and compact and repair.

 

[Guest]

Joan...

Thank you for your response. I had considered that after reading some
information in the Microsoft solution center. However in my latest case, I
looked to see if there was an "ldb" file...there wasn't one. Our computers
have a program called DeepFreeze on them, which puts a "Thawspace" as a
virtual drive on the C:\ drive. The computer reboots to its preset condition
every 45 minutes if no activity takes place on the computer. The database I
have created resides on the thawspace. It is possible that these secretaries
have been working in the database, walked away from the computer and had it
reboot while the database was open...however all have told me that is not
what happened.

It seems that I have seen an ".ldb" file on some of my previous problems,
but hadn't read the solution at the time. I will look for it in the future
and see if that will fix the problem. Again...thanks.

 

[Joan Wild]

Joan...

Our computers have a program called DeepFreeze on them, which puts a
"Thawspace" as a virtual drive on the C:\ drive. The computer reboots
to its preset condition every 45 minutes if no activity takes place
on the computer. The database I have created resides on the
thawspace. It is possible that these secretaries have been working in
the database, walked away from the computer and had it reboot while
the database was open...however all have told me that is not what
happened.

I wouldn't put the database there, as you run the risk of corrupting it.

You could have the database close, if no activity occurs so that it is
closed properly. Look for KickEmOff at
http://www.datastrat.com/Download2.html

It seems that I have seen an ".ldb" file on some of my previous
problems, but hadn't read the solution at the time. I will look for
it in the future and see if that will fix the problem. Again...thanks.

Every time a mdb file is opened, and associated ldb file is created in the
folder, so you should see one if the mdb is open. When the mdb closes, the
ldb is deleted.