John W. Colby
jcolby at ColbyConsulting.com
Fri Mar 28 09:21:18 CST 2003
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 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 _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com ---------------------------------------------------- Is email taking over your day? Manage your time with eMailBoss. Try it free! http://www.eMailBoss.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 3540 bytes Desc: not available URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030328/59130187/attachment-0001.bin>