Database Title Changes to db1, then db2, then db3, etc. What's Happening?

[InDFW]

It makes copies of itself - some can be opened, some cannot.

I try to delete the smallest-sized ones before anyone does any work in any of them, and my department has accepted the fact that our database does this and our database is named "db1" or whatever number is the current one for the day, but I'm not getting any help from our IS department. I don't know how to fix it and I'm worried we are going to lose data as a result of this issue.

This may not be an Access problem? I tried Googling, but must not be using 'good' terms or phrases because I am not getting any good hits.

I'm desperate - can someone please throw me a bone?

 

[HiTechCoach]

I think you mean the file name changes not the database's title property inside the database.

Your issue of the database getting renamed is probably because a compact/repair fails.

You need to make sure that compact on close is turned off!

It also sounds like this is a multi user database that has not been properly split into a front end and back end.

Is your database split? If not, this must be done ASAP! This should also fix your issue of the database getting renamed with the compact fails.


See:
Sharing a database

 

[InDFW]

Your issue of the database getting renamed is probably because a compact/repair fails.

You need to make sure that compact on close is turned off!

thank you - that article looks exactly like what i needed!

regarding the compact error - is this somthing that should be addressed? i thought it was good to have compact on close turned on?

 

[HiTechCoach]

I ALWAYS, ALWAYS ALWAYS do a backup, or two, before I run a compact. I have see a compact corrupt a database beyond any ability to repair it. IMHO, the Compact on close should be removed. It is just to dangerous. I have seen to may people lose data using the "Compact on Close" to make it worth using.

To compact a shared database, like a back end, you must make sure that all users are logged out of the database. You also must do the compact from the machine where the data is located. You do NOT want to compact a database across a network connection. This is also something you are currently doing which is probably part of your problem.

If each user has a copy of the front end on their local machine, and the compact on close runs, it will only compact the database on their local machine. When the compact fails, then you can just copy a new front end form the server.