Installing an MDB

[piccpp]

I have created a basic application in Access that has Forms, queries and
tables(Local and linked(SQL)). I recently released the application to some
users and have noticed that the size of the MDB is increasing. The
application only allows the users to inquire and produce reports. I would
expect the size of the MDB to remain the same. If you have any ideas, I
would appreciate it. Thanks

 

[Douglas J. Steele]

Access often needs to create temporary objects when it's running queries.

 

[Chris Mills]

Access often needs to create temporary objects when it's running queries.I wasn't really aware of that, though I can hardly disagree. I would have
thought that if piccpp was really only doing enquiries and reports, then it
(they) could try setting it to "read-only" and see what happens.

The question is how much size increase. If just a bit, then who really cares?
I would bet they are doing more than read-only...though not with my own money
of course.
Chris

 

[Mel Woolsey]

Over time the growth in the size of the frontend can get to be significant.
In Access 2003 (and 2002??) in design mode under Tools/Options you can
indicate that you want your program to be Compacted and Repaired each time
it exits, which keeps it at its original size.

Regards,
Mel Woolsey

 

[Chris Mills]

I actually disagree with that (though it's only my opinion).

1) Compacting as regularly as probably multiple times a day is vastly
excessive (one-a-month would be more normal, or less often even than that)
2) Compact-on-close wastes closing time! It may arguably be more susceptible
to corruption, the more they compact (but I won't push that)
3) If the database is split into Front-End/Back-End, Compact-on-close won't do
nothin' for you.

I believe the "best" approach is to provide them with a "repair/compact"
shortcut, both for the FE and BE, which they can run as necessary or as takes
their fancies.
Chris

 

[Mel Woolsey]

Chris,

I agree with you on the frequency of compacting the backend. However, the
frontend grows in size faster than the backend, and there is very little
risk in compacting it on exit since if it gets currupted, it is easy to
replace (unlike the backend data).

One of the reasons we may disagree is that my users only start and stop my
application once a day, and closing time is not an issue.

Regards,
Mel