Compact FE ?

  • Thread starter Thread starter Jerry
  • Start date Start date
J

Jerry

Since a front-end database does not have "data" is there
any need to have it compact and repair on close? I will
be creating an MDE to distribute but I am not sure if I
need to leave the compact/repair on close checked. Also
should the backend be set up to compact/repair on close
instead of/in addition to the FE? If so when does the
compact occur if multiple users are linked to it?

TFH
Jerry
 
Actually, compact/repair on close has no affect on the backend, since you're
not actually "in" the backend. Yes, this is a nuisance: there's nothing
built into Access to allow you to regularly compact the backend.

It's moot whether to leave it on for the frontend. If your application
generates dynamic SQL, for instance, then compacting the frontend regularly
makes sense.
 
Doug

What is considered dynamic SQL - I have quite alot of VBA
code with SQl statements for insert,delete and updates,
would these be considered such? I was compacting in hopes
of reducing the FE database size (close to 20mg, 8mg MDE),
is there anything else that I should look at?

TFH
Jerry
 
Yes, if you've got SQL statements in your code, it can conceivably lead to
bloat. Take a look at the file size before and after you use the database to
get an idea of how bad it is.
 
I was compacting in hopes
of reducing the FE database size (close to 20mg, 8mg MDE),
is there anything else that I should look at?
Click to expand...

20 Mb to an 8 Mb MDE is a bit suspicious. I find that an MDE is about
75% the size of the original MDB. I presume the 20 MB of the FE is
after compacting.

Trouble is I'm not sure what it would consist of. Hmm, there was a
bloating issue with menus.

I'd try importing all your objects into a few FE, compiling and see if
it gets smaller. Also do a decompile but do that as a separate step
to see if it'll help.

Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
start-up times
http://www.granite.ab.ca/access/decompile.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
of reducing the FE database size (close to 20mg, 8mg MDE),

If you are doing a lot of importing data to a temporary
table, you should consider using a temporary database
for your temporary data.

If not, consider importing all objects to a new database.

If you really did mean milligrams, ignore this post :)

(david)
 
Back
Top