[AccessD] Replication - A2K

John,

But what about the situation where a customer calls back five minutes
later with additional information and gets a different examiner?  How is
the second examiner going to be able to get to the customer's data if
you replicate on a 15 minute schedule?  This may not be a common
occurrence, but it does happen and you need to be able to handle it.
And don't expect the customer to remember the name of the first
examiner, that solution is a non-starter.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us


 -----Original Message-----
From: 	accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]  On Behalf Of John W.
Colby
Sent:	Thursday 2003 Mar 27 20:38
To:	accessd at databaseadvisors.com
Subject:	RE: [AccessD] Replication - A2K

Precisely (on both counts).  There are about 25 users of the database.
Virtually ALL of the users are actively editing specific cases.  Each
case can be handled by anyone, i.e. the first examiner available in the
phone queue picks up the phone, opens the record for the person that the
phone call is about.  In the process of taking the call, info is usually
entered into "contact" logs, i.e. info about the phone call.  Each
claimant's file has an assigned "Examiner" who "runs" the case.  That
person has to make phone calls to physicians, witnesses, employers etc.
Those phone calls also get data logged about them.

As you can see from the description, there is not a high degree of
concurrency where several people will be in the same case at the same
time.  My observation of the operation is that there is a very random
pattern of data entry since the incoming phone calls are random.  There
is also a fairly predictive data entry since a case has to be worked,
however this side of the operation is not necessarily data entry
intensive, nor holding records open for long periods of time.  The
Examiner calls the physician and requests a doc.  Notes that fact in the
log, moves on to the next claim.

It seems that this type of operation would be perfect for replication,
on a 15 minute (or even longer) replication schedule.

John W. Colby
Colby Consulting
www.ColbyConsulting.com