Database Backup?

[eggy168]

Our network database has a miscellanous problem recently that one of our databases in our network has a backup copy recently.

We had this issue before, the name of the database then there is a number right next to it, ex: xxx.mdb is the name of the database, then there is another database in the same folder, xxx1.mdb. Then I asked around the office and I found users didn't have patient to wait the database to be open, they clicked the database again, and therefore the xxx1.mdb created by the system. However, the problem is being solved after I told people the way to open the database, there is no more xxx1.mdb.

However, I found there is another issue this couple weeks beside the xxx1.mdb, it is the new name under the same folder, xxx_backup.mdb. I believe this time someone manually re-name the database, it can't be someone quickly open the database to create the xxx1.mdb. I asked around the office and checked who did the backup and no body said yes to me which I know people hate to saying it is their faults.

Therefore I tried to find who was the last person to modify the database, like what was the last save time or who the last modified of the datbase, I found Access 2000 doesn't provide such information, not like other Microsoft office that there is an Author section under the property.

I want to know is there any way or any software I can purchase to find who manually save the database in the network folder? Or anyone thinks it is a bug from Microsoft Access 2000?

 

[PHV]

Nobody has converted or repaired the database ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[eggy168]

No as far as I know.

 

[ProgramError]

Access sometimes creates its own backup if it had a problem loading the backend. Well it seems to do in 2003! You may find it will make numbrous backups with the postfix xxx_backup#

Program Error
Programmers do it one finger at a time!

 

[RoyVidar]

Are everybody logging into the same database? If so, you should consider splitting into a front end (FE) and a backend (BE). Let the BE reside on the server, and let each user have their copy of the FE on their local drive, which is linked to the BE. The database splitter wizard (Tools | Database Utilities) will probably do an OK job with it (but be sure to have backups before doing it).

I don't believe anyone has saved these files manually. Starting with the 2002 version (I think, i can't remember seeing it in previous versions), when there's a problem (as pointed out by ProgramError), and you get the "sorry for the inconvenience" message, I think Access routinely creates such backup when closing after chrashing like that.

I'm perhaps very paranoid, but I would take such signs as a possible starting corruption, and carefully examine the database for any signs of corruption.

There should be plenty information to be found through search both on splitting the database, and recovering from corruption, should this be the case.

Roy-Vidar