I'm in trouble now...

[SaraMegan]

Okay, so I'm probably the most inexperienced Access user/programmer among us, but I just started three weeks ago with no prior knowledge whatsoever, and I think I've been doing okay...

Until, that is, my database decided to not be a database anymore or something.

Okay, so the database I created was put out on the server at work, and I was working with it and the server went down. It bit... anyway, I had to hit control+alt+delete to get out of there, and now when I try to reopen it, it tells me that it is no longer a valid database, and would I like to try to fix it? Of course, I say yes, but then it tells me it can't.

My question is... is that true? Is there really nothing I can do?!?

The good news: I back up my database, but I haven't since yesterday noon, and I've made quite a few changes since then...

I really appreciate all your help. It's nice to know there's somewhere I can go to get my questions answered by nice people.

--Sara

 

[David R]

You might be able to Import most of the objects...

Open a new clean database. First Import your data tables, if you've got any real data in them. File>Get External Data>Import. Make sure those load fine in your new database. Then Import your queries, and probably your independent Modules/Macros. See if that works. Then try your reports and forms one by one, closing and reloading the database each time. If you get to one that crashes it, make a note.

Make periodic new backups while you do this and always revert to an older one if you get to a point where you can't load the database again. Then try to Import from yesterday's backup the forms/whatever that wouldn't import correctly.

Hopefully that'll save you most of your work. Ctrl-Alt-Delete on an open database is a nearly surefire way to corrupt the database, sorry to say.

 

[SaraMegan]

No such luck...

I just tried importing all my data... I went to import, opened up the database, it asked me for my password, which I put in, then it popped up a window saying "Unrecognized database format" then showed the path to what I had just tried to import.

I'm super frustrated and I just got to work 15 minutes ago.

Is there any hope at all? Or should I just attempt to re-do all of what was done since Thursday?

Thanks for your help.

--Sara

 

[David R]

Not sure... never crashed a database that hard.

However, here's a couple more ideas:
1) Make sure the database is still in the correct format. If it was in Acc97, make sure it wasn't saved as Acc2k. Open it with the latest version of Access anyone has available, just to be sure.
2) Make sure there isn't a .ldb file stuck in the folder on the network. Sometimes a database that doesn't shut down properly will leave the lock file (.ldb file) hanging. Delete it if there is one, and try again.
3) Search all forums for "unrecognized database format". There are some other responses posted, including a possible solution by Carol if you can get ahold of her.

Otherwise you may be shafted...

Good luck,
David R

 

[SaraMegan]

Sucking it up

Thanks, David R. For all your wisdom.

After the grouch in me went for his coffee break, I was able to suck it up and just backtrack a day and a half... It's a little more work than I wanted, as I have to track down all of the data that was inputted by other people around the office, but things are much better now.

I'm just here in a temporary position working on this project. When I'm all done, I have to teach it to the lawyers and secretaries in the office, and then I'm moving to Illinois. What can I advise these people to do so they don't make the same mistake and end up making me move back? What do I tell them to do if the server goes down and they don't know what to do with their database cuz it went all loopy?

Thanks again.

--Sara

 

[David R]

Have you split the database?

If they have a front-end with forms, queries, reports, etc, and a back-end with tables, linked to the front, that may help protect your data better. Also the back-end will be noticeably smaller so backing it up at the end of every day will not be so onerous. The front-end only needs to be backed up when some element in it is changed, like a form or code module.

Access, like many Windows programs, is somewhat susceptible to crashes. The best you can do is track down why it happened and try to prevent it from happening again. And safeguarding data - I'm glad you only lost a day and a half.

Wisdom? Youre funny, Sara.

 

[Alexandre]

Sara,

There is a free utility from MS called JetComp which is able to repair a corrupted DB in a good many cases. It is easy to use. I may be worth to provide a copy to your users.
Regular backups are also a good advice to give to users, and it is not a too difficult feature to add to a DB neither.