Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database growth in Access XP

Status
Not open for further replies.

beetee

Programmer
Jan 31, 2003
660
MX
Has anyone else noticed that database sizes seem to grow tremendously in Access XP after minor editing (e.g. changing the size of a control on a report, a database grew from 5 Mb to 35 Mb). The database is a FE database, with a few small local tables used for caching network data; however the same app on Access 97, after much editing, would maybe get to 12 Mb. The XP version has grown as large as 150 Mb.

A Compact operation sometimes shrinks the database somewhat, but not down to it's nominal size. MDE files generated from the database have a reasonable size.

A work-around I have been using involves translating to 2000; performing a command line /decompile /compact, and translating back to XP. Obviously this is a poor method.

Perhaps I'm missing some vital new setting:

[x] Inhibit Untoward Database Growth.
 
beetee,

Something really sounds wrong with your Access FE.

I would suggest creating a new Database and then importing everything from your database in question.

1) Open your Existing Database, open a code module and then go to TOOLS>References and note all references in your original db.
2) Create New DB, and set all the references to match old db.
3) Import everything from the old db to new access db
4) Open Code window, and compile the new Access DB. (must do this immediately after the import completes!)
5) Now backup the new DB.

Hope this Works For You,
Hap [2thumbsup]



Access Developer [pc] - [americanflag]
Specializing in Access based Add-on Solutions for the Developer
 
Thanks for the answer Hap!

I did do that once, but it was some time ago. I have a lot of inertia for that solution because the database is secure, and different objects have different group-wise permissions. However, it's probably worth another attempt. And I'm paid by the hour.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top