Problem while Compacting Database

[Idris]

Dear Friends

I have a .mdb password protected with all types of objects (tables, queries, forms, reports, codes, functions, modules, etc) they too are password protected in VB, the .mdb works fine but when I tried to repair and compact the database from the menu tools option, very recently it started giving me the message of database has been corrupted and requires tobe backedup before proceeding with the repair options and the log report of this corrupted .mdb file is to be sent to microsoft for the review.

In short i am not able to compact the Database though it works fine - but the moment I try to compact it gives me this problem - I am worried and concerned as its looks good but what happening in the background can anyone in here sugguest the remedy or the precautionary measures.

This file is on the network shared by min 2 person at the same time.

Please advice - thanks

 

[ghudson]

You should decompile the db. Then compile it then compact/repair it. Make a backup before you do that! Search around if you do not know how to run those functions on your db.

 

[iangirven]

Idris,

additionally make sure the databse is not in use by any other users when trying to compact and repair.

 

[Idris]

Thanks - looking for tips on how to decompile??? and yes I did make sure that no one is logged in.

I am planning to do, is to create another blank.mdb and then import all the objects - how's that? any comments plz

 

[Ashfaque]

Idris,

I think it is better to make another blank db and import all the object including your custom menu if any. This is what I also did a year back.

Regards,
Ashfaque

 

[Ashfaque]

One more thing, use alway MDE file and not the MDB. MDE file is already in compressed mode and there is rare chance of getting damaged. And even if it happens, immediately you could make another copy from MDB which any programmer should keep reserve.

Regards,
Ashfaque

 

[iangirven]

Idris,

I have used that method on occasions which usually works. However sometimes there is a problem with a specific table that I cant import. I usually refer back to my latest backup and import the data for the table from that one. Unfortunately this does mean some data loss, but as the db is backed up each day this is minimal.

regards
ian