[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

Access creating additional database files upon close

Posted on 2011-09-07
7
Medium Priority
?
279 Views
Last Modified: 2012-05-12
I searched but couldn't find the answer i was looking for. I have an Access database that multiple people use shared from a server. I've noticed lately that in the same folder as this database, there are other multiple databases named such:
Database1.mdb
Database2.mdb
Database3.mdb
...and so forth.

Could anyone tell me why Access is creating these files, how to stop it, and if it is safe to delete them? Also, i have Compact on Close disabled for this database.

Thank you.
0
Comment
Question by:jbarnette
  • 4
  • 2
7 Comments
 
LVL 7

Accepted Solution

by:
BusyMama earned 100 total points
ID: 36498680
I can't guarantee this is your cause, but I have seen similar issues in the past when a database compact and repair is interrupted or for some other reason not completed.  I have always deleted them without issue.  You can try opening them to see if there's anything lurking in there .... :)
0
 

Author Comment

by:jbarnette
ID: 36498785
Thanks for the reply. The problem that occurred was that I had up to 5 people in there at one time and somehow up to 12 database.mdb files were created. Then some other folks came and entered information into the mdb files instead of the accdb file. Now i have some info in the main database, and other info in these ghost databases that were created and it's become a nightmare. I basically deleted the mdb files and told them to reenter the information; however i need to find out how to prevent this in the future. I've also heard of the compacting issue, but there was no compacting with this database during these occurrences.
0
 
LVL 49

Assisted Solution

by:Dale Fye
Dale Fye earned 100 total points
ID: 36498825
You should NEVER tell people where your application or the data is sitting on your server.  They should all have their own front-ends on their PCs, which point to the backend data sitting on your server.

You can tell whether anyone is in any of these databases by checking for the .ldb or .laccdb file associated with the mdb or accdb.  If the lock file doesn't exist, it is OK to delete the datafile.  

I don't envy you having to check all of those databases for data that was entered into the wrong mdb file.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 

Author Comment

by:jbarnette
ID: 36498903
I understand...but is there a way to prevent these additional database files from being created?
0
 

Author Comment

by:jbarnette
ID: 36502878
You should NEVER tell people where your application or the data is sitting on your server.  They should all have their own front-ends on their PCs, which point to the backend data sitting on your server.

Ok. so i split the database. Now i have a front end with all the forms, reports and such and it is distributed to the desktop of each person's workstation via a logon script. This front end database has linked tables to the backend database.  Is this what you are suggesting? Did i do it correctly and do you think this will resolve my issue?

Thank you.

0
 
LVL 49

Expert Comment

by:Dale Fye
ID: 36503411
The login script is a great way to put the latest version of the application on their desktops.  There are other methods, but that one generally works well.

As BusyMama stated the problem with the additional databases is generally created by a unsuccessful compact/repair operation.  Since you are redeploying the front-end each time your users log on, I'd make sure that the Compact On Close setting of the Front-end is set to No.  This should hopefully resolve the issue of the duplicate Database#.mdb files.

The other problem you are likely to have is that you have users that are familiar with where the application used to reside, so you may still encounter problems with them going directly to that folder on the server and attempting to open the database from there.
0
 

Author Closing Comment

by:jbarnette
ID: 36503455
Thanks for the great tips! I'm going to ensure the compact on close is disabled on the front end application and we'll see how it goes.
Thanks!
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows how to get a list of available printers for display in a drop-down list, and then to use the selected printer to print an Access report or a Word document filled with Access data, using different syntax as needed for working with …
Implementing simple internal controls in the Microsoft Access application.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…
Suggested Courses

607 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question