[AccessD] Replication - A2K

John,

I'm not saying your solution doesn't work.  I pointed out a situation
that will arise and that they need to have some procedure in place to
handle it.  Whether that procedure is within your solution or something
they will have to handle manually is for them to decide.

As to how often such calls occur, all I can say is when I worked for my
Dad in his insurance agency it happened several times a day that
somebody would call to file a claim but didn't have all the information
the agent needed so they would have to call back later with the
additional information.  I doubt that human nature has changed much in
the intervening years.

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:	Friday 2003 Mar 28 09:21
> To:	accessd at databaseadvisors.com
> Subject:	RE: [AccessD] Replication - A2K
> 
> They need an answer, and can't afford SQL Server.  This is an answer.
> To not look at the realistic options because of the 1 in 1000 (or
> whatever) occurrence is not realistic.
> 
> I am certainly open to other options.  However they just spent 8
> months moving an old creaky flat file to a relational MDB FE/BE.  They
> don't have a budget for a $10,000 solution at the moment.  What
> solution can they get for $500?  Moving to SQl Server will be $5k or
> more.  They don't have that, they have said so.  I have done all of
> the typical "make sure the fields are indexed" things.
> 
> So rather than saying "this solution doesn't work", why don't you
> suggest a solution that does?
> 
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Wortz,
> Charles
> Sent: Friday, March 28, 2003 8:33 AM
> To: accessd at databaseadvisors.com
> Subject: RE: [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
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030328/c2c95e9a/attachment-0001.html>