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

Computer bloat question

P: n/a
I'm sure there are causes for computer bloat. I've wondered if it came
from running queries. I have lots of queries that are created within my
forms, sometimes reports and modules. Are these the culprits? How
about if you had a query that you constantly changed the SQL? Or is it
caused simply by the use of adding/deleting/modifying the records.
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
The majority of Access bloat is not b/c of adding data to tables or
running queries, it is a result of just running and/or changing things
within your db like forms, reports, and other programming objects.
Right click your db, select Properties, and mark how big in MBs it is.
Then open your db and choose Tools -> Database Utilities -> Compact and
Repair Database. Now close it and recheck the size. Mine went from
12.3MB to 2.1MB the first time I used it.
Streamline1000

Salad wrote:
I'm sure there are causes for computer bloat. I've wondered if it came from running queries. I have lots of queries that are created within my forms, sometimes reports and modules. Are these the culprits? How
about if you had a query that you constantly changed the SQL? Or is it caused simply by the use of adding/deleting/modifying the records.


Nov 13 '05 #2

P: n/a
Chuck Grimsby wrote:
On Wed, 02 Feb 2005 21:16:34 GMT, Salad <oi*@vinegar.com> wrote:
I'm sure there are causes for computer bloat. I've wondered if it came

from running queries. I have lots of queries that are created within my

forms, sometimes reports and modules. Are these the culprits? How
about if you had a query that you constantly changed the SQL? Or is it
caused simply by the use of adding/deleting/modifying the records.

Yes, Yes, Yes, and Yes.

Compacting (as suggested by st************@gmail.com) only gets rid of
the "bloat" (which is, in reality, "Working Space" for JET) until the
next time you run the query that needed the space. Of course, that
means that Access will have to stop to expand the MDB file, negating
all that time you spent doing the "Compact and Repair".

A properly developed Access database doesn't need to be compacted. I
have several that haven't had that operation run on them for several
years.


So what is a properly developed database? One that uses queries listed
under the query tab only? I have a few crosstab reports crosstab, that
I need to generate new recordsources. Also my forms are constantly
creating dynamic queries and I would not want to get rid of them and
only use those queries under the query tab.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.