Impact of compacting database

[Guest]

Hi all,

I have an application in ASP that has its backend in Access 97. It has now
reached 1GB size limit. I would like to know if I compact the database, would
it lead to any loss of scripting/macros or its mapping info to network
servers or any other relevant rules applied on it? Any advice would be
greatly appreciated and helpful.

Thanks,
Ash

 

[Rick Brandt]

Hi all,

I have an application in ASP that has its backend in Access 97. It
has now reached 1GB size limit. I would like to know if I compact the
database, would it lead to any loss of scripting/macros or its
mapping info to network servers or any other relevant rules applied
on it? Any advice would be greatly appreciated and helpful.

Thanks,
Ash

Compacting is completely harmless IF the file is not corrupted in any way.
If in doubt make a copy first.

 

[Rick Brandt]

Hi all,

I have an application in ASP that has its backend in Access 97. It
has now reached 1GB size limit. I would like to know if I compact the
database, would it lead to any loss of scripting/macros or its
mapping info to network servers or any other relevant rules applied
on it? Any advice would be greatly appreciated and helpful.

Thanks,
Ash

One thing to add is that compacting is actually the creation of a new file
with a temp name. After the compact is successful the original file is
deleted and the new one renamed. This can cause the file's network
permissions to change as the new file will typically inherit the settings of
the folder.

 

[Guest]

Hi Rick,
I've been working on an application for a few months and the file has grown
to 40 megabytes. After closing it this last time, it is suddenly 9 megabytes.
A quick review looks like it's fully functional, but this is a shock.

Does Access automatically compact the DB at a certain file size?
Thanks,
Karl

 

[Douglas J Steele]

The only time Access will automatically compact a database is if you've set
it to compact on close (under Options in Access 2000 and newer)