Software

Ask something
Discussion Locked

Access Database compression

0 helpful
9 replies

by andy bettoni

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've a problem with a compression of a large Access database. It's now 115 Mb and it continues to receive data from a PABX. I'd like to compact the database in order to improve its perfomance, but every time I launch the process Access program goes in crash. I use a Pc with Win98 SE, 256Mb Ram e 2 Gb of free space on hdd. Could anyone suggest a workaround?
Thanking much.
Andy

9 replies

by mackem

Hi There.
There are a number of things you could try, but before you try anything, remember to take a back up copy first.
You could try a database repair, this could remove any errors and enable you to comapct the database. Also a database of this size should be spit into front end back end. To do this you should go to the Tools menu, then Add in's and Database Splitter. This keeps the tables away from the main body of the database and helps prevent corruption.
If the repair does not workyou could make the database an .MDE file instead of .MDB this gets rid of all of your code and also compacts the database at the same time.
Hope this has been of some help.

by andy bettoni

I cannot create an .mde file because the database is the base of thirdy part application. Idem I cannot split the db with the "splitter". I can try with the repair before the compact.
Tks.

by donq

What you are doing should work? Maybe you don't have exclusive rights to the database as it may take 5 to 10 minutes depending on network config, cpu speed, etc....

Do you use Tools | Database Utilities | Compact and Repair from the main menu, and do you rename or replace existing .mdb file?

I would replace when no one else could open or access the database. IT MUST be opened exclusively.

by andy bettoni

I tried both options from the menu You suggest. The database is opened exclusively (no body has access to db).
The problem is that Access goes in crash after few minutes of work.
Tks.

by otl

From what you have told us it appears the PABX may be to blame, continues to receive data from the PABX.

Unhook the PABX connection and when no one else is in the database compact and repair it.

Answer #2 is partially correct but missed the PABX.

by andy bettoni

I work off line from the PABX: I copied the db from the PC connected to PABX (stopping data transfer) to my develop machine, then I compact the db and when terminated I'll copy the compacted db to original machine. I did this operation two timesbefore this and I didn't have problems.
I'll try with the option repair
Tks.

by is

Sometimes the simplest thing to do is to create a brand new database and import all of your objects. This will automatically compact your database and may take care of your problem in the meantime. When you are done just rename the database to what it needs to be. It seems to remove unseen clutter from the database and should take care of your problem.

This discussion is closed to new replies.