Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / February 2005

Tip: Looking for answers? Try searching our database.

MDB Size increases rapidly

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ed Kopta - 03 Feb 2005 18:02 GMT
I have an Access 2002 mdb that increases in size about 6-12MB when I use a
particular form that automates a data-entry operation. Highlights of this
operation are:

1) Create two temporary tables (one a subtable of the other) by using VBA to
copy tabledefs
2) Get data by opening Excel in the background and cycling through targeted
cells
3) Using action queries to fill data from temp tables to original ones, and
also to fill other tables with new data (these other tables hold text values
from the worksheet that are related to the original tables by primary key
values).

I understand that I can always compact very frequently or code a menu
command to do so, but I was wondering if there are any other general
principles involved that would allow me to address this issue more
elegantly. Maybe there are some classic no-nos involved with the above
operations. Has anyone dealt with problems like this?

Thanks for any help you can give
-Ed Kopta
Marshall Barton - 03 Feb 2005 19:24 GMT
>I have an Access 2002 mdb that increases in size about 6-12MB when I use a
>particular form that automates a data-entry operation. Highlights of this
[quoted text clipped - 14 lines]
>elegantly. Maybe there are some classic no-nos involved with the above
>operations. Has anyone dealt with problems like this?

Creating tables and deleting/adding records is a major cause
of bloat.  This kind of operation should be avoided if at
all possible.  Unfortunately, Import operations often do
benefit from th use of temp tables.

If you can not find a reasonable way to avoid them, then you
should place them in a temporary database.  Here's a good
way to manage the ins and outs of all this:
    http://www.granite.ab.ca/access/temptables.htm

Signature

Marsh
MVP [MS Access]

Ed Kopta - 03 Feb 2005 20:27 GMT
That link looks promising. Thanks for the help!

-Ed Kopta

>>I have an Access 2002 mdb that increases in size about 6-12MB when I use a
>>particular form that automates a data-entry operation. Highlights of this
[quoted text clipped - 28 lines]
> way to manage the ins and outs of all this:
> http://www.granite.ab.ca/access/temptables.htm
David C. Holley - 04 Feb 2005 05:20 GMT
You may also want to consider procedures. Do you have to import the data
 hourly or will daily do?

>>I have an Access 2002 mdb that increases in size about 6-12MB when I use a
>>particular form that automates a data-entry operation. Highlights of this
[quoted text clipped - 26 lines]
> way to manage the ins and outs of all this:
>     http://www.granite.ab.ca/access/temptables.htm
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.