Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Missing Database

Status
Not open for further replies.

bcooler

Programmer
Jun 13, 2009
132
Here's a weird one.

I store an Access 2007 file (approx 8meg) called "R&R Database.accdb" on a network location (165GB free disk space) with read/write/modify permissions to everyone on the network. I have twice run into a problem where the file has gone missing and all that's in the network folder is a file called "database.mdb", which I believe is a temporary file that Access creates when compacting/repairing? I set the file to compact/repair every time the user closes Access.

The real problem is that the users don't realize the file's gone and just start writing to the "database.mdb" file. I add back a previous saved version (sometimes hours or days old) to the network folder, but I then have to ask the users to re-enter their data.

1.) What's going on here? What do I need to do to stop this problem?

2.) Is the "database.mdb" file an accurate file for me to use?
 
I would make sure the application is split into a front-end (for forms, reports, queries, and code) and back-end (for tables). Each user should have their own copy of the front-end and share the back-end on a network. Users should never open the back-end directly.

Duane
Hook'D on Access
MS Access MVP
 
I don't disagree, but don't know if this would help the current issue.
 
This was a bug in 2007! Go to Allen Browne's site at


and scroll down to "What's Broken (New Bugs)"

Now scroll down to the bottom of this table and you'll see the fix for this problem.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!
 
Thanks for this information! I looked at it and it does sound like my problem (hard to tell because the users of the database would most likely be the ones to see the error). However, I am running SP2, while the bug report suggests this failure is fixed by SP2.

Do you think SP2 may still be having he problem? If so, have you heard of any fixes?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top