[AccessD] VBA Unbound data entry / update form

LOL.  Tell that to the client.  They tell us what to do, not 
the opposite.  I recommend, they say "we want it this way", 
I say "ok".

There is a lot of "bad design" out there, and in the end we 
(or I) do what the client wants.  BTW they hire me to work 
for them.  Each of the principals make several times my 
annual wage, and their business is booming.

Do you need their phone number to tell them all about their 
"bad design"?    8-)

John W. Colby
www.ColbyConsulting.com


Stuart McLachlan wrote:
> Aaaaaaah!   That's just plain bad design.
> 
> If a  person is talking to an operator, there's no way they should be ABLE TO change what 
> has been recorded by another operator talking to a different person let alone FORCED TO.  
> 
> Each conversation should be a separate record in a child table - with separate fields for a 
> timestamp, who the caller is and who the operator is.
> 
> 
> On 27 May 2008 at 22:51, jwcolby wrote:
> 
> ... 
>> 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.
>>
> 
> 
>