One thing you can do that usually reduces the size is to decompile. But make sure you have a backup as the /decompile switch is undocumented and while I've never had a problem with it there is no guarantee. See FMS's Article at www.fmsinc.com/microsoftaccess/performance/decompile.asp
Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT http://thatlldoit.com
MS Access MVP
http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852
My Nothing-to-do-with Access blog
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Thursday, October 29, 2015 2:27 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] File Size
I've always wondered if there are some things I could do to reduce the file size of an Access database. I can compact/repair all I want, but the size still is bigger than I would think it should be, and grows very quickly after compacting. Are there consistent things in particular that tend to make an Access database overly large? I'm talking about an empty shell without any data in it!
Does the number of tables, forms, reports, etc. make a significant difference? How about the number of fields in a table? I don't have any graphics on forms other than maybe some lines and boxes. Are there any general rules that I should follow in order to keep the file size down or is there any way I can parse out what parts of the file are the culprits causing the file size explosion?
Thanks for any suggestions.
Posted by: "Bill Mosca" <wrmosca@comcast.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (6) |
Tidak ada komentar:
Posting Komentar