Dawn,
 
    In conventional set up, when composite value for a group of fields is required to be unique, violation if any, at data entry stage, gets detected only when the user tries to move to the next record. This can be quite inconvenient, after the effort spent in making  entries into a large number of controls for the record in question.
 
    My sample db  Forms_CheckReqdAndDuplicates  might be of interest to you. It is available at Rogers Access Library (other developers library). Link - http://www.rogersaccesslibrary.com
 
    This db provides instantaneous real time friendly warning if the data entered in a field (which belongs to the group of fields whose composite value is required to be unique) would lead to a violation. The focus stays at the offending field.
 
    You could adapt the underlying approach suitably, for your specific needs.
 
Best wishes,
A.D.Tejpal
--------------
 
----- Original Message -----
Sent: Saturday, October 01, 2005 01:49
Subject: [AccessDevelopers] Getting Duplicate Records

OK - I have a client table.  ClientID is the primary key.  As much as I have tried to train the two people who are doing the data entry in the database to Check to see if a client is already in the database, I now have 387 records which appear to be duplicates.
 
How do I fix the data entry Form so that it checks to see if there is already a matching record in the database?  I think if I confirm that there is already a record which matches txtFirstName, txtLastName, and txtTitle and throw up a flag, that I can stop most of the duplications.  (These are the first three fields which would be entered)
 
Suggestions?
 



Please zip all files prior to uploading to Files section.




YAHOO! GROUPS LINKS




Reply via email to