Developer Forum

Hi,

I'm an Access newbie and was wondering if someone could
1. confirm the following steps are correct, and
2. let me know if I'm missing anything.

-- I have an Access database application which eventually
will be used by multiple users and multiple departments.
-- The tables and relationships will remain the same for
all departments, though some departments may not use a
particular table.
-- The forms, queries & reports are same for all
departments to begin with, but some departments will
request additional forms or reports in the future specific
to them.
-- There may be some changes in table design (minor, I
hope!) to accommodate specific department needs (eg. Dept
A may want to capture more information than Dept B
regarding a system entity).
-- Access 2000, on Windows 98.
-- The data entered by one department will be shared by
all (periodic synchronization).

Here's how I think I'll implement this:

1. Split the database into front-end (with forms, reports
and queries) and back-end (with tables).
2. Create a replica of the back-end, one for each
department.
3. Have a design master to make changes in table design.
4. Have one replica connected to the Design Master, and
then connect Department replicas to it.

DM ---- Replica 1 ----- Replica Dept A
| |
| |
| |
Replica Replica
Dept B Dept C

5. Maintain a copy of the front-end for each Dept in my
working directory, so that if I make any changes to the
forms/reports for a specific department, I can simply copy
them to the front-end database for that department.

I'm not quite clear on how I will connect a front-end to
the Replica for that Department though. What are the steps
for doing that? Right now, I have one database with
everything in it. I know how to split the database, and I
know how to create a replica, but if someone can fill in
the gaps, and/or point me in the right direction, I'll
appreciate that.

Thanks!

-Amit

Do all the departments have shared access to a single network share?
If so, you can mount a single database there for concurrent access by
all users, thus making replication unnecessary. Depending on your
database design and the number of concurrent users, performance may be
good or bad.

You can find a tool for distributing new FE to users at
http://www.yqcomputer.com/

Otherwise, you have covered the bases. Isolating the DM is the correct
choice.

The method for the departments to synchronize with the hub will depend
on your setup. There are at least three choices:
- manually open the departmental BE and synchronize with the hub
- include VBA code in the FE to perform the synch on demand.
- use the Replication Manager that is included in the Access
Developer's Edition.


On Fri, 14 Nov 2003 09:43:11 -0800, "Amit"




=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd

i Jack,

Thanks for both your replies.

network share?

Yes, they do. And, all the replicas will reside in
different folders on the same shared drive.

concurrent access by
on your
performance may be

This was discussed, and the decision was to use
replication as the number of concurrent users eventually
will be in the range of 30-50+. Plus, possibility of off-
site data entry. Do you think this justifies using
replicas instead of using a single database?

I do have Replication Manager, so hopefully, this won't be
too much of a problem.

Thanks again!!

-Amit

is the correct
hub will depend
the hub
demand.
Access
eventually
specific
Dept
reports
copy
steps
I

On Tue, 18 Nov 2003 09:16:34 -0800, "Amit"



With off-site data entry, replication is certainly warranted.

With 30-50 concurrent users, it depends... if they are just "readers",
that's one thing. If they are 30-50 "editors", then you are pushing
the limits. A more typical range would be 10-20 users, maybe even
fewer, but it all depends on your skill in writing well-designed
multi-user apps.


RM is fairly straightforward to set up. You should certainly use a
replica farm as explained on www.trigeminal.com

=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd

Definitely "editors".

Thanks again for your reply. And, I'll check out the
trigeminal website.

-Amit


Depending
warranted.
just "readers",
are pushing
maybe even
designed
be
certainly use a