Problems with database size

[PlamenGo]

Hi,


I have an Access application, which was created in '97 version.
During the years we moved to 2K, 2003, 2007, and now I am trying to go to 2010, using the Web version.
I have redone all tables, and when importing all forms, queries, reports and macros, the size of the application was 32 MB (original size - 24 MB).
For some demo purposes, I needed to reduce the application, and I started by compressing a copy in ZIP folder, then deleting tables, forms, reports -everything I thought useless for the demo ...
For my surprise, instead of shrinking, the database grew up to 80 MB (76 MB after "Compact and repair")
When Unzipping the original(32MB), after open and close, the size became 86 MB (82 compacted).

Any ideas or help how to deal with this problem?

[pkstormy]

I would create a new accdb and then import just the needed objects.

One thing I found which can make the MSAccess file grow is pictures. For example, copying/pasting a picture from a word document (or a large bmp/jpg/etc...) picture will make a big difference in the accdb size versus if you paste it from a small size bmp/jpg/etc... file.

For me, I've always gotten concerned when the mdb/accdb grows beyond 50 meg. If it does grow beyond 50 meg, I then create a new mdb/accdb and then link (I use SQL Server tables), and then importing the queries, forms, modules, etc...

[PlamenGo]

Thanks for the reply.
I have have tried several solutions, similar to your suggestion, the problem is still here.
Is it possible the problem to be in the Web format of my database? I read somewhere that Access 2010 creates hidden copies of the tables when an user of the web format is logging to the application?
PS. I don't have any pictures, just tables, forms with VBA code, queries, macros

[pkstormy]

Is this an *.accdb file or does it have a different extension?

[PlamenGo]

it is an .accdb, and I need it as .accde but 2010 "loses" just 2-3MB, when making the exec file ...

[pkstormy]

An 82 meg accde seems a fair amount larger than normal (especially since the tables would most likely be linked to an accdb backend). Unless there's a lot of 'temp' type tables with a lot of data, there must be a lot of forms/reports in it.

Have you tried compacting/repairing using a different computer?

If you've created a new accdb, imported all the objects, and then created a new accde, I might do this again but this time import form by form and look at the size after importing each form/report to see if there's one culprit form/report that is causing it to bloat so largely.

[PlamenGo]

Thanks!
The problem is not in the importing procedure :
I have saved as 2003 .mdb all forms and queries ( I need the tables compatible with 2010 Web formats), after the import the size is around 24 megs, after opening to check interoperability, the size increases to 43 ... ( I tried to remove all useless tables and forms)
My problem is I have a lot of VBA code behind the forms and I need to be sure the application isoperating ...

[pkstormy]

I'm not understanding but something still doesn't seem right on the large size of this.

I'm confused when you say "after opening to check interoperability, the size increases to 43 " it bloats to 43 meg from 24 meg? Are you making temp tables in this process? Or what is happening at this point? The accdb should not bloat when you run it unless you're making temp tables. Are the data tables themselves in this accdb or are they linked tables (to another accdb) which they should be.

FYI:
Importing into a new accdb (one form at a time) and compacting/repairing after each import, then checking the size, will tell you if you have one specific form or report that is somehow bloated. That form/report should then be deleted and re-designed from scratch and then re-imported. I will often see a particular form or report which causes an mdb/accdb to bloat the size beyond what it should.

[PlamenGo]

1. open to check interoperability: wrong exprecion, sorry!
I am starting the 24 megs application and checking how it works - several (important functions). When I exit (auto compact and repair), the size is 42-43 ...
2. This specific appication was desighned in early 1996-1997, using Access '97. I have all tables need in it (in part of them I work register data some of them I use as temporary, I have labelled them as WRK_xxxx,) .No table is created ordeleted during the operation.

[pkstormy]

Split the database to a frontend/backend.