[AccessD] VBA Unbound data entry / update form

Drew Wutka DWUTKA at Marlow.com
Tue May 27 22:06:17 CDT 2008


Ack...sputter....cough.... did YOU build that system for them?

Take it easy on me JC, I didn't announce it here (the OTers know), but I
had a heart attack a few weeks ago (long story...I'm quite fine!).

What you are talking about is exactly what I am talking about, but you
are saying 'they want to do it that way, and it works for
them'....ummmm, then why are you trying to find out what's going wrong?
;)

This is where an unbound form would work for you.  You don't work on ONE
record, you create NEW records, but make it look like one record.  

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, May 27, 2008 9:51 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] VBA Unbound data entry / update form

 >Why would you EVER have two people making changes to the 
same field in the same record at remotely close times?

Two of my applications are call center databases.  In one 
case insurance claimants call in to the call center to talk 
to the adjuster or other call center operators.   There are 
30 such operators.  A person calls in (or the adjuster calls 
out).  A record is created in a "contact" form describing 
the call.  It is just the way that they do business that 
they "group" information in the same record in some cases. 
They might talk to the sister of the claimant.  The time is 
recorded and who talked to them, the conversation etc.

The sister might call back 10 minutes later with more 
information, EXCEPT that the call is taken by some 
completely different operator who pulls up the claim record, 
looks at the "contact" record, and starts editing that same 
exact record, adding more information provided by the sister 
of the claimant.

That is just the way that they do business.  They have 
contacts with a dozen to a hundred DIFFERENT individuals 
concerning details of the claim, everyone from relatives, to 
lawyers to physicians to private investigators, to the 
courts, to the IRS...  Not all claims have contacts with all 
of these kinds of individuals, but any may have contacts 
with any of these contact types or all of these contact 
types.  The company finds it convenient to just keep editing 
one record with conversations with a Private Investigator 
for example.  They MAY create a brand new record for the PI, 
particularly if the date / time is widely separated, or they 
may not.

Many people, potentially editing the exact same record, 
often within minutes of each other.  Edits in the Claim 
records tend to "burst", with bursts of edits in specific 
areas of specific claims within minutes, hours or days, then 
total inactivity for hours, days or weeks.  IOW they "work" 
specific claims to the point where activity dies down, and 
then they might not do anything in that claim until letters 
are received back, phone calls are returned etc. which can 
provoke another "burst" of activity.

Many people, potentially editing the exact same record, 
often within minutes of each other.  You may call it bad 
design if you wish, but that is they way they do it, that is 
the way they have always done it and they are not interested 
in your critique of their methods.  What matters is that it 
works for their purposes.

Now... one person starts an edit and goes to lunch...

John W. Colby
www.ColbyConsulting.com

The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.





More information about the AccessD mailing list