Overall size keeps GROWING 1

[ds2728]

In testing my current project, one of the processes deletes all records from one table then goes through a process to repopulate that table with the most current information.

Through the testing process I have run this process many times and I just noticed that the size of the database has grown to twice it's size in megabytes. I am sure that space is not being released and so it just grows.

1.) Is this what is happening to me?
2.) How can I prevent this from happening?
3.) If I can't prevent it, is there a process I can run to pack the database to recoup this space?

Thanks,

dave

 

[Maquis]

You just need to compact the database. It's under Tools ---> database utilities (Access 97). Access will take disk space whenever it needs it to enlarge a object, but it nevers gives the space back without compacting.

I believe Access 2000 has an option to automatically do this when you close the database, but I'm not sure since I'm still on Access 97.

 

[THoey]

Just as an addition to Maquis' great explanation, this is the way Access handles everything, from data to forms to reports, etc. If you create a form, blow it away and then recreate it, that old version is still in the MDB, it is just hidden from view. The only way to clear this is to compact.

Good job Maquis... Terry M. Hoey

Please read the following FAQ to learn how to help me help you...

faq183-874

 

[Databaseguy]

Yeah, I've had a Db go from 2Meg to 200K after some serious development then a compact afterwards.

If you want to do it programatically, use the CompactDatabase method.

 

[Maquis]

Heck, that's nothing. I took over design of a database from some users who didn't know what they were doing.

When I first got the database it was 150meg. I couldn't even open it on my computer, because I am not allowed to "own" that much network space. After redesigning it, it is now about 9meg. (Oh, and those users are not allowed to touch the design view now!)

 

[CPUburn]

hi y'all,

one little extra consideration: I had a db which was compacted every week resulting in a 38Mb database, I read it over into another db: result 14MB ---> sure worth a try!!

CPU-burn