Problems Compacting

[StateSQLboy]

I have recently run into an issue regarding the ability to compact my database. I have several linked tables to my application. Whenever I try to compact the database, It gives me an error and then won't finish. Could this occur from haveing too many tables with similar of the same column names?

 

[psemianonymous]

Database corruption happens unfortunately often. It's probably nothing you did--probably. In any case, head on down to the link below for help on how to get your database up and working again.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[scriverb]

I don't think that should be an issue. I would suggest making a copy of the your database. Then remove the linked tables. Just right click on the linked tables and select delete. This will not delete the data or the tables in the back-end(BE) databases. Now try Compacting the databases. If it finishes, great!! Now re-create the linked tables to your front-end(FE) database.

If the compact failed that you may have a corrupt database. You could try decompiling the database and then recompiling it. The try the Compact process.

Let me know what you find.

Bob Scriver

 

[StateSQLboy]

I had already resorted to an earlier version of the app. When I link the tables and try to compact I get this error:

The Microsoft Jet database engine couldnot find the object 'MSysCompactError'. Make sure the object exists and that you spell its name and path correctly.

 

[psemianonymous]

Similar threads on Google:

http://groups.google.com/groups?hl=...t+MSysCompactError"+&btnG=Google+Search&meta=

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[JoyInOK]

You'll also get an erroron compact if you do not have enough space on your C: drive. Even if the database resides on a network, and you have a second hard drive, the program will make a copy of your database and place it on the C: drive before it attempts to compact it.
The strange error generated is usually something like "Microsoft Access cannot find the field 'xxxxx'"

 

[philcon]

Hi Bob (S)

Your solution does work as the problem relates to the linked tables, but does anyone have any idea WHY the linked tables cause this problem?

Only asking as I have run into it for the first time, yet this is not the first database I have tried to compact with linked tables.

Regards


Phil.

 

[scriverb]

I don't know why this happens but I know it has worked for me in the past. The linkeage process may have been the part of the database that was corrupt. By removing the links the compacting and repair process can be successful. Then relinking them straightens things out.

Don't get me wrong I have compacted databases with linked tables and everthing works just fine. It just happens that sometimes there is a problem with that part of the database.

Bob Scriver

Nobody believes the official spokesman... but everybody trusts an unidentified source.
Author, Bagdad Bob???