mdb Size

[Guest]

Dear Sir/Madam,

I'm developing a program, that although not very
sophisticated, it is very intricate. I notice that as I'm
developing and running the program (in MSAccess 2002 on
Windows 2000 Pro). The file starts getting larger (e.g.
goes from 10 meg to 99meg). When I do a "Compact and
Repair Database" the size drops to 10meg. I tried to
incorporate the "Compact and Repair Databaase" function
into my program, but get a message saying I can't do that.

Is there a way I can control the size of the file in the
backgroumd without always doing a "Compact and Repair
Databaase".

Thanks in advance for your help,

Burt

 

[John Vinson]

Is there a way I can control the size of the file in the
backgroumd without always doing a "Compact and Repair
Databaase".

In Options, you can set the database to "Compact on Close".

 

[Tom Wickerath]

Hi Burt,

Here are some KB articles that you might want to check out, in case the bloat is related
to any of these issues. Note: Some of the articles indicate Access 2000. I'm pretty sure
that they apply to Access 2002 as well.

ACC2000: Database Bloats When Importing Large Text File
http://support.microsoft.com/?id=239527

To Help Prevent Database Bloat, Explicitly Close Recordsets
http://support.microsoft.com/?id=289562

ACC2000: Manipulating Objects with ADO May Cause Database Bloat
http://support.microsoft.com/?id=199005

ACC2000: Manipulating Objects with DAO May Cause Database Bloat
http://support.microsoft.com/?id=197953

If you are creating temporary tables within your database, you may want to create a
separate mdb file on the fly, and then create the temporary table within it that you need.
Then create a link to this table using VBA code. That way, a temporary database can bloat
without affecting your working database.

Tom
___________________________________________


Dear Sir/Madam,

I'm developing a program, that although not very
sophisticated, it is very intricate. I notice that as I'm
developing and running the program (in MSAccess 2002 on
Windows 2000 Pro). The file starts getting larger (e.g.
goes from 10 meg to 99meg). When I do a "Compact and
Repair Database" the size drops to 10meg. I tried to
incorporate the "Compact and Repair Databaase" function
into my program, but get a message saying I can't do that.

Is there a way I can control the size of the file in the
backgroumd without always doing a "Compact and Repair
Databaase".

Thanks in advance for your help,

Burt

 

[Guest]

Thanks Tom. I'll check those sites.

Burt

-----Original Message-----
Hi Burt,

Here are some KB articles that you might want to check

out, in case the bloat is related

to any of these issues. Note: Some of the articles

indicate Access 2000. I'm pretty sure

that they apply to Access 2002 as well.

ACC2000: Database Bloats When Importing Large Text File
http://support.microsoft.com/?id=239527

To Help Prevent Database Bloat, Explicitly Close Recordsets
http://support.microsoft.com/?id=289562

ACC2000: Manipulating Objects with ADO May Cause Database Bloat
http://support.microsoft.com/?id=199005

ACC2000: Manipulating Objects with DAO May Cause Database Bloat
http://support.microsoft.com/?id=197953

If you are creating temporary tables within your

database, you may want to create a

separate mdb file on the fly, and then create the

temporary table within it that you need.

Then create a link to this table using VBA code. That

way, a temporary database can bloat

 

[Guest]

-----Original Message-----


In Options, you can set the database to "Compact on Close".



.
Thanks John. I hope it works.

Burt

 

[Tom Wickerath]

I haven't tried it yet, but there is a posting on the Access MVPS site that may be related
to your original statement: "I tried to
incorporate the Compact and Repair Database function into my program, but get a message
saying I can't do that."

http://www.mvps.org/access/general/gen0041.htm

Going from 10 MB to 99 MB, and then back to 10 MB after compacting is not normal, in my
opinion. Are you attempting to import OLE objects (images and/or other binary files such
as Word documents) into your database? This is generally not recommended due to the bloat
issues.

Tom
___________________________________


Thanks Tom. I'll check those sites.

Burt
___________________________________

Hi Burt,

Here are some KB articles that you might want to check out, in case the bloat is related
to any of these issues. Note: Some of the articles indicate Access 2000. I'm pretty sure
that they apply to Access 2002 as well.

ACC2000: Database Bloats When Importing Large Text File
http://support.microsoft.com/?id=239527

To Help Prevent Database Bloat, Explicitly Close Recordsets
http://support.microsoft.com/?id=289562

ACC2000: Manipulating Objects with ADO May Cause Database Bloat
http://support.microsoft.com/?id=199005

ACC2000: Manipulating Objects with DAO May Cause Database Bloat
http://support.microsoft.com/?id=197953

If you are creating temporary tables within your database, you may want to create a
separate mdb file on the fly, and then create the
temporary table within it that you need. Then create a link to this table using VBA code.
That way, a temporary database can bloat without affecting your working database.

Tom
___________________________________________


Dear Sir/Madam,

I'm developing a program, that although not very
sophisticated, it is very intricate. I notice that as I'm
developing and running the program (in MSAccess 2002 on
Windows 2000 Pro). The file starts getting larger (e.g.
goes from 10 meg to 99meg). When I do a "Compact and
Repair Database" the size drops to 10meg. I tried to
incorporate the "Compact and Repair Databaase" function
into my program, but get a message saying I can't do that.

Is there a way I can control the size of the file in the
backgroumd without always doing a "Compact and Repair
Databaase".

Thanks in advance for your help,

Burt

 

[Tony Toews]

If you are creating temporary tables within your database, you may want to create a
separate mdb file on the fly, and then create the temporary table within it that you need.
Then create a link to this table using VBA code. That way, a temporary database can bloat
without affecting your working database.

FWIW see the TempTables.MDB page at my website which illustrates how
to use a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm