By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,656 Members | 1,027 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,656 IT Pros & Developers. It's quick & easy.

"Bloating" in Access

P: 1
I am using Access 2003 but my Access file is in 2000 format. I have deleted some data (some unused customers in the "Customer" table and some old Orders from the "Order" table). I did this to try and reduce the size of my file.

I have tried the "compact on close" but that does not make a difference in the size of the file.

Does anyone have any suggestions?

BTW - this file has gone thru numerous revisions over the years.
Feb 26 '08 #1
Share this Question
Share on Google+
4 Replies


Minion
Expert 100+
P: 108
I am using Access 2003 but my Access file is in 2000 format. I have deleted some data (some unused customers in the "Customer" table and some old Orders from the "Order" table). I did this to try and reduce the size of my file.

I have tried the "compact on close" but that does not make a difference in the size of the file.

Does anyone have any suggestions?

BTW - this file has gone thru numerous revisions over the years.
I wish there was a good answer to this question, but without knowing all the ins and outs of the db it's hard to say for sure. However, from the sounds of it the db has been been around for a while an has collected plenty of information over the years. As such reduction in size may not be possible due to the number of records. If this is the case you may look at making another db and exporting some of the unused records to it for storage purposes. These table then could be linked to the active db incase the records need accessed occasionally.

Hope this helps.

- Minion -
Feb 26 '08 #2

missinglinq
Expert 2.5K+
P: 3,532
Exactly how big is this database, and approximately how many rrecords did you delete? Bloat means different things to different people!

You should know that using the Compact On Closing option is considered to be a very bad idea by most developers. Compacting can lead to database corruption, and as such should always be preceeded by making a backup.

Welcome to TheScripts!

Linq ;0)>
Feb 26 '08 #3

P: 1
I read the other thread regarding bloating, which I have the same situation. Here is the thread

I have a FE/BE 2007 db that grows as I watch. I can even close all forms and remove any active module and it still clicks along at exactly 20KB every few minutes. It seems to grow with more users accessing it. We have the FE on a corporate windows shared drive, and the backend in the same folder. I am moving towards putting a client copy on the users machine and using one of the "update" scripts around to keep their copy current. The FE compacted size is about 12MB, at the end of the day it usually reaches 35-40 MB. I do not have any tem tables, appends, updates or anything. Everything is hooked to the BE tables. I noticed that when using the 2003 version of the same DB, with Access 2003, we did not have this problem. Is it an issue with Access 2007?

Help

Doug Mc
Mar 5 '09 #4

P: 1
We experienced the same problem after going to Office/Access 2007. After much ado, we paid for a Microsoft Incident. They admitted that there was a bloating problem and advised us to apply Service Pack 2. This fixed it.
Apr 27 '10 #5

Post your reply

Sign in to post your reply or Sign up for a free account.