Access database automatically creates a new database

[sk88]

So I have a database called 'Final_ABC' (example) that was working perfectly fine until recently. Don't know what happened but I noticed that the database created 3 copies of it in the same folder. They are called Database, database1, and database2. They are all in mdb files and the database has all the forms and tables I created for Final_ABC database. I tried googling and I can't seem to find an answer. Hopefully someone will be able to help me with this.



Thank you in advance

[JoeM]

Do you have "Compact on Close" turned on, or some other automated "Compact and Repair" feature going on?
I have seen that happen with "Compact of Close".

Also, how many different people are using the database?
Are multiple people using it at the same time?
If so, have you split the database?

[sk88]

Thanks JoeM. I just checked my database and I do not have the "Compact on close" turned on.
There are about 3 people using the database as this database is sitting on a shared network drive. I didn't have this problem before (for at least 2 years) and I am not sure why it is happening all of a sudden :/

Do you have "Compact on Close" turned on, or some other automated "Compact and Repair" feature going on?
I have seen that happen with "Compact of Close".

Also, how many different people are using the database?
Are multiple people using it at the same time?
If so, have you split the database?

[CJ_London]

the one question you have not answered is - have you split the database?

[sk88]

Sorry Ajax. No, I don't have the database split.

the one question you have not answered is - have you split the database?

[JoeM]

It is strongly recommend you do use if you may have concurrent users.
Typically, you split the database into a back-end that houses just the data, and into a front-end that has all the other objects, and give each user their own copy of the front-end.

This should help cut down on issues like this.
See: https://support.office.com/en-us/art...3-51b1d73498cc

[sk88]

Thank you JoeM. I will give it a try and let you know if it worked.

It is strongly recommend you do use if you may have concurrent users.
Typically, you split the database into a back-end that houses just the data, and into a front-end that has all the other objects, and give each user their own copy of the front-end.

This should help cut down on issues like this.
See: https://support.office.com/en-us/art...3-51b1d73498cc