Spurious Database Creation

  • Thread starter Thread starter PhotoFinish
  • Start date Start date
P

PhotoFinish

Hi.
We recently switched our disk drives from Novell to Active Directory.
Now, I am noticing that on our share disk, where several Access Databases
live,
we are getting "extra" databases:
db1.mdb, db2.mdb, etc. We are up to db42.mdb at this point, and
they appear to be copies of the back end database (Access 2003).
What is causing them, and how do I stop it?
Also, some of them I can open with no issues, others say I don't have
permission to open and to talk to the administrator (who would be me --
I have no idea what to tell myself).

I have a sneaky suspicion they are being created when I do backups, although
I put the backup databases in a separate drive, and I make sure the .ldb is
not
set when I start the backup.

Ideas?
Thanks for your help.
 
On Thu, 27 Aug 2009 11:44:01 -0700, PhotoFinish

Probably created when someone does a Repair & Compact and does not
finish the job and the temporary file is left behind.
A2003 has a "compact on close" option that is particularly annoying
and should be turned off in most cases.

-Tom.
Microsoft Access MVP
 
Thanks. I will check that out.
Is there a better way to see what users are on before
starting the backups/compressions? Right now, I just
have a batch file that checks for the .ldb file.
 
Back
Top