The database is indeed just one file. I thought it should be
split, but never having done it before and the database being so
stable I didn't attempt to split it - If it aint broke don't fix
it is my usual policy!
If it's not split, it's already "broke," in my opinion.
The idea of splitting the database has raised all sorts of
questions from various users. Here are some of them.
If you could answer any of them it would be most appreciated
QUESTIONS
a..
The answer to question a. is "".
b.. Should the front end be converted to a mde file before
distributing?
Distributing as an MDE has certain advantages (no loss of global
variables on an unhandled error, smaller size, no decompiling, no
ability for users to edit, slightly faster execution in some cases),
but also can have disadvantages (no ability to fix a bug for a
single user in their MDB without pushing out a new MDE, potential
problems in a mixed environment with multiple versions of Access on
the desktop of the users).
c.. Are there any disadvantages to splitting?
It can cause a decrease in performance, but usually it's not one
that matters except in cases where the original monolithic app was
incredibly badly designed.
d.. Would I need a copy of Access 2003 installing on my pc as
well as 97
Not sure I understand. If you have a split database, you can leave
the back end tables in A97 and create your front end in A97 for the
A97 users, and then convert to A2K format for your A2K3 users.
Splitting makes this *easier*.
e.. How easy to update front end?
As easy as FILE | COPY. It can be easily automated with tools like
Tony Toews' front end updater utility.
f.. Would I need to convert a copy to 2003 so I could distribute
to 2003
users.
Ideally, you'd distribute to those users in A2K format, which is
usable in A2K, A2K2, A2K3 and A2K7, whereas A2K3 format is usable
only in A2K3 and A2K7. Of course, since your app derives from A97,
there is no advantage at all to using the A2K3 format, since you
won't be taking advantage of any of the features added in A2K3 that
make its format different from A2K2 or A2K.
But it *is* possible for an A97 MDB to be enabled to run in later
versions of Access. I don't know how complete that is, though, nor
how stable.
g.. if I had my back end in 2003 would access97 users be able to
use it?
Absolutely not.
See answer to question a.
i.. Should I e-mail a copy of the front end to all users, and
will I need
to send a new version out if I make any amendments to the form.
If so how can I be sure that the user will use the new version.
If you use an automatic update like Tony Toews', then you won't have
to worry about it.
j.. Will the table links work across different networks?
If they are mapped appropriately, or dynamically re-assigned at
runtime, yes.
k.. Some offices use the same public folder. Can I place a copy
of the
database in the public folder (max of 2 people would use it at any
one time - the are 16 people in one office for example but only 2
pcs, or would it be better to send them a copy each.
Each user should have a separate copy of the front end.
l.. Every ones personal files are stored on one of our networks
- can the
database be stored with these documents or should it be stored on
the workstations hard drive, ie C drive. ( we have staff who use
more than one pc and staff who share the same pc).
I'd store it on the C: drive if the domain policies allow it because
then the front end doesn't have to be loaded across the network. But
chances are that there won't be a huge difference between these two
alterantives.
