J
JaRa
Hi,
Normally you compact your database through Tools>Database Utitlities>Compact
Repair.
Now this works fine except when you write a lot of VBA code. You will notice
that your database keeps on growing even after compacting.
There are 2 solutions to get it down to its real size:
1) Create a new database and import all the necessary objects from the old
database and don't forget to set the references back (Not funny Procedure)
2) Open your database in another version of access. E.g. I have a
development running on Acccess XP which I opened with Access 2003
surprisingly enough after compacting this database it went down to it;s real
size.
The reason for 2 to work is because the compilation model was changed from
Access XP to Access 2003 so basically they discard all previous code
compilations and temp bulk.
Isn't there a feature available in XP or 2003 to get rid of all the
compilation bulk?
So that we don't have to do 1 nor 2. If not will this be taken care of in
Access12?
Normally you compact your database through Tools>Database Utitlities>Compact
Repair.
Now this works fine except when you write a lot of VBA code. You will notice
that your database keeps on growing even after compacting.
There are 2 solutions to get it down to its real size:
1) Create a new database and import all the necessary objects from the old
database and don't forget to set the references back (Not funny Procedure)
2) Open your database in another version of access. E.g. I have a
development running on Acccess XP which I opened with Access 2003
surprisingly enough after compacting this database it went down to it;s real
size.
The reason for 2 to work is because the compilation model was changed from
Access XP to Access 2003 so basically they discard all previous code
compilations and temp bulk.
Isn't there a feature available in XP or 2003 to get rid of all the
compilation bulk?
So that we don't have to do 1 nor 2. If not will this be taken care of in
Access12?