compact and repair design question

S

scott04

Is it a good idea to place a command button to compact if your splitting the
DB and placing on network drive?
 
R

Ron2006

Is it a good idea to place a command button to compact if your splitting the
DB and placing on network drive?

Unless you really aren't using the tables file of a split db it will
need repair and compacting.

However you CANNOT do it while any users including the FE of a split
DB is linked into the tables. This is particularly true if you follow
the suggestion of having a table in the BE file always linked to the
running FE through some form that is always open. This keeps a link to
the table on the network open and speeds up the operation of the FE
since it does not have to establish a dynamic link every time you run
a query. And as long as there is even 1 FE linked in this manner
(including the one you are in) you cannot get control of the file to
do the compact.

For my applications, I have created a separate application that has a
table of Application table mdbs and that checks for the ldb file and
when they push the button (or double click) then it will do the
compact and repair on that table. In this app it keeps the last file
size (and the date/time of the last compact) and computes the current
file size so you can get a feel of whether you need to do a compact.

Ron
 
K

Klatuu

It it is multi user, definitely not.
Even for a single user, I would suggest opening the back end and compacting
manually.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top