I am currently working on an mdb and am concerned regarding it's size. It's up to 15.9MB and am about half done. Included in this so far are 24 forms, 8 reports and a single module. I have less than a dozen records at the moment. And only about 10 jpegs (the Company Logo-required by my employer). I'm concerned by the time I'm complete it will be a real fat, slow beast!

This seems rather large for what it contains. I've compiled, compacted and repaired. The machine I'm working on has A2003 on it but the mdb is in A2K. I have no extra add-ins (other than DAO library- which I need (would it add overhead anyway?). And I have just the usual code for validation and record processing.

1) COuld someone tell me, doesn't this seem a bit large?
2) Is there a way to tell the size of the individual objects? (I've already tried the "Documenter"- no luck. "Killing" a copy of one form and then compacting showed a 100KB size difference.)

Thanks,
Loralee

I believe you can create an Mde version that should be a bit smaller and a bit faster.

Also if it ends up too big you could create a couple of databases, one that contains your data and quesries, the other that contains the forms.

btw, 15.9 mb doesnt sound all that big.

Hi,

   The reason the mdb file is probably so big already is that you are still designing it. During design, it can get pretty large, even with no data.

   In Access, go to Tools > Options, and then select the General Tab. In the lower left, select Compact on Close. This is an important option during design. That should start to reduce the size of the file.

Does this help?



mmcdonal

Another possible cause of large dB size other than not compacting it is your table design. Here are some things that could make the dB bigger.

1) Are your tables normalized? Are you repeating data in tables instead of storing them once only?

2) Are you storing calculated values? In a word, DON'T!

3) Are you storing photographs or clip-art? In a word, DON'T! Store the path and file name to them and link to them, but don't actually store the actual picture.


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

You can use the images as form backgrounds, for example, by pasting them in the forms. I find that doesn't add much to file size. However, if you store them in tables as OLE images, the file size will grow exponentially.


mmcdonal

Thanks, Guys.

It's normalized Most of the tables are look ups (not using the wizard) and referenced via SQLs. The only images are small jpegs (the company logo). It just seems big at this stage for so little test data.

Thanks