Corrupt... .bkf AND .mdb

[blyxx86]

I was doing a backup yesterday to one of the network drives. I usually do a daily/weekly backup. I made some modifications to the disk that the database was being stored on to improve read access times and data retrieval speed. However.. after these changes were made succesfully I went to backup the database like I usually would...

What happens? Blue screen about 60% through the backup. Corrupting the backup file and the reboot of the computer erased the database (it was being stored on a RAM Drive, but it was also being saved to an .img file so I thought I was safe, those were not updated with the database information.)

I had two backups... one that was done nightly, and one that was done throughout the day (saving the database to the .img file).

Now, I'm stuck with a broken database and I'm unsure what to do.

I was able to recover the backend .mdb (not the front end - but that's less important) but when I try to 'repair and compact' Access just freezes.

I have tried the Jetcomp.exe (i believe is what it was called) to try that. It didn't work either.

I'm currently trying to use 'undelete' programs to recover the lost .mdb file that got deleted from the .img file but have not had a whole lot of luck yet.

Any suggestions, perhaps to free .mdb repair programs? I'd prefer not to spend money on this, as the database isn't extremely important, but I lost about 400 records (about one week) worth of input.

[NeoPa]

I guess you put this one down to experience and never go without backing up properly again.
Cold comfort, I know, but although this will stay here and there will be an opportunity for anyone to post more help, I doubt it'll get any. Even in the Windows forum (I'd normally suggest trying that out for a question like this) I doubt you'll get much joy I'm afraid. Not that there's much harm in trying.
Good luck.

[MMcCarthy]

I was able to recover the backend .mdb (not the front end - but that's less important) but when I try to 'repair and compact' Access just freezes.

See can you import the tables from the backend file into a new database.

[blyxx86]

I was able to successfully view many of the 'new' fields (the weeks worth of information) that I was missing using a program I found on the internet, but it is $299 for purchasing. I suppose I could justify the information with the company.

I thought my database was being backed up. I used to run the backup manually to ensure that there were no errors, but when I put it on a schedule I never saw any error messages when I came in the next morning, so I was under the assumption that there were no problems. The update file was even being 'modified' daily. I'm not sure what happened to the backup schedule, but it got broken somewhere along the way.

Lesson learned. Not too difficult to replace, but still kinda is sucky.

I'm programming a new backup schedule that is going to store it in more than one location.

I was doing a phantom backup at one point, but I felt it was just a little too demanding for what the database is worth (not critical information).