I know this topic has been floated around a bit, but I don't see any easy solution.
When developing a new projrct or editing an old one, the Front End size grow and can be compressed.
I was keeping an eye on it with this last new project. My front end code base got to about 12 megs compressed. I thought that wasn't too bad, until...
For shxts and grins, I created a brand new database and imported everything from the 12 meg one. This is a pain to get all the code references reset in the correct order. The resulting file size? About 5-6 megs.
Now why couldn't the repair and compression tool do that?
There is NO data stored. This is a code base front end only. I had the options set to compress on exit.
Does anyone else have this issue with ACCESS 2000 and XP?
Thanks
Dave
When developing a new projrct or editing an old one, the Front End size grow and can be compressed.
I was keeping an eye on it with this last new project. My front end code base got to about 12 megs compressed. I thought that wasn't too bad, until...
For shxts and grins, I created a brand new database and imported everything from the 12 meg one. This is a pain to get all the code references reset in the correct order. The resulting file size? About 5-6 megs.
Now why couldn't the repair and compression tool do that?
There is NO data stored. This is a code base front end only. I had the options set to compress on exit.
Does anyone else have this issue with ACCESS 2000 and XP?
Thanks
Dave