"Donald Watson" <RE**********************@linncountyrec.com> wrote
in news:2q**************@news.uswest.net:
One question. Using the Front End/ Back end version. Wont my
users need to export modified reports or forms back and forth to
all 5 copies of the front end for them to be accessible by
everyone?
We have 5 users on this particular database and any of them may be
making changes or adding queries, reports or forms to the
database.
Well, wake up and smell the coffee: with Access 2000, Microsoft
changed the way code is stored in an Access MDB, and two users
*can't* edit the code/objects at the same time. There is no getting
around that under any circumstances.
MS's reason for this was that it prevents corruption, but it's a
kind of corruption I never ever saw in any of my clients' MDBs.
Also, because it converts your Access project into a single record
in a Jet data table (that's why only one user can edit it at a
time), you can't save incremental changes -- any SAVE of anything
has to save the whole record. This is not nearly as slow as it was
in the initial release of A2K, but it is still slower than A97 (and
annoying, because of the multi-save dialog, which drives me crazy).
Your only answer for this is to have front ends for each user and
some method for saving their new reports to a reference copy of the
front end, then a method for pushing those changes out to the end
users.
I suspect, though, that most of these saved reports are highly
redundant, for instance, being the same report layout, but using a
filtered recordsource. This can be handled by a little programming
to allow an end user to choose their recordsource, either by
filtering or picking from a list of queries.
Your current setup is now completely unworkable.
It was previously working only by pure luck.
--
David W. Fenton
http://www.bway.net/~dfenton
dfenton at bway dot net
http://www.bway.net/~dfassoc