Drew Wutka
DWUTKA at Marlow.com
Wed May 28 12:41:50 CDT 2008
EXACTLY!!! Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Wednesday, May 28, 2008 12:12 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] VBA Unbound data entry / update form 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. > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.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.