Error Access

[Tauri]

Can anyone help me with a little, big problem?

Wend im trying to open my database this error message shows up.

"Microsoft office has detected curruption in this file. To try to repair the curruption, first make a backup copy of this file. Them, on the tool menu, point to database utilities and click compact and repair database. If you arecurrently trying to repair this curruption then you will need to recreate this file or restore it from a previous backup"

Help?

 

[MStef]

It means that your MDB is in corruption status.
1) Make a copy of MDB.
2) Make a COMPACT and REPAIR database.

 

[Tauri]

I already did that. It doesnt work. The same message shows up.

 

[Dennisk]

One of the options is to create an empty db and import all your objects from the corrupted db., however if your db is well and truly corrupted you will require a restore. or you will need to purchase a program to recover your data. I have a recovery program but it will only recover the tables, no indexes and autonumber are converted to numbers. - good luck

 

[Tauri]

Ill try that, Gracias lolol

 

[Tauri]

No good. The same f...... message shows up.

 

[The_Doc_Man]

I cannot offer a solution for your current problem. I can offer advice on how to protect yourself from future massive disruption.

Backup the database to any removable media that can hold it. Like burn a CD or drop it on a USB drive or something. Make a schedule of backups and adhere to it. Keep old copies for a set period before destroying or recycling them.

There are other threads in this forum you can find with the SEARCH function on "Database Corrupt" and "Preventing Corruption"

My advice only has value when corruption has kicked in so badly that you are, well, exactly where you are right now. Which is to say, belly up in the tank. With a backup copy, you can step backwards just a little bit and play catch up. Hope there was nothing valuable in that DB because right now it might as well not exist.

 

[Moniker]

Along the lines of what Doc Man is saying (and he's right), you need to make a backup at least two times a day, if not more. It's even better if that backup is to an external memory source (CD-Writer or USB Drive). I prefer a USB Drive because they're a lot less hassle, and you can get a 2GB USB drive for $17.99 here:

http://www.newegg.com/Product/Product.aspx?Item=N82E16820134043

Basically, you want to backup around 10am, 1pm, 4pm, and whenever you stop for the night (6-8pm for me). Make a naming convention that's easy so that you can remember where you are. For example, today I'll have these files for the DB I'm writing:

DBName_2007-05-16a.zip
DBName_2007-05-16b.zip
DBName_2007-05-16c.zip
DBName_2007-05-16d.zip

Assuming I have no corruptions at the end of the day, I'll delete the a-c versions and remove the "d" from the last version. (Note that I use the format "_YYYY-mm-dd" at the end of the filename as that makes them sort correctly.) Then I keep each day's worth of changes for around 2-4 weeks, depending on how much progress is being made. Eventually the directory will look like this:

DBName_2007-05-07.zip
DBName_2007-05-08.zip
DBName_2007-05-09.zip
DBName_2007-05-10.zip
DBName_2007-05-11.zip
DBName_2007-05-12.zip
DBName_2007-05-13.zip
DBName_2007-05-14.zip
DBName_2007-05-15.zip
DBName_2007-05-16.zip

And so on. At a certain point, it no longer makes sense to maintain such a backup log -- you may have a different schedule than me; it's whatever you're comfortable with. Also, since USB drives are big and cheap now, space shouldn't be a concern when maintaining these backups. In other words, you could hold the last 50 DBs (a month and a half or so) on the key without worry.

The big, obvious advantage to this is avoiding what happened to you. It's saved me more than once in my years of work. Another, perhaps indirect advantage, is that the time it takes to compact/repair your DB, close Access, zip (or rar or whatever) the file, and copy it to the USB drive gives you a chance to stop staring at your project. Sometimes, a little distraction is a good thing. We've all been at the point that we've been staring at a problem for so long, the answer that is staring back at us is not obvious until we stop staring for a few minutes.

 

[Dennisk]

Further to backing up.
When I start a database include a version number in the filename

ie db_10.mdb then as I develop I compact then create another version
ie db_11.mdb. I do this at regular intervals say twice a day. so if anything goes belly up before the days work is backed up (all my dev. is on a network drive) I lose no more than 4 hours work.

 

[neileg]

Have your tried the Microsoft Jet Compact utility? It's a free download.