andysgirl8800
Registered User.
- Local time
- Today, 10:10
- Joined
- Mar 28, 2005
- Messages
- 166


Would it help if I let you know the form (frmHalfTab) I am using the button (cmdDuplicates) on is built on a query (qryHalfTab2) which is built on my table (tblHalfTab2). The SQL for the (qryHalfTab2) is as follows:
SELECT tblHalfTab2.MemberNum, tblHalfTab2.MBRLast, tblHalfTab2.MBRFirst, tblHalfTab2.MRBAddress, tblHalfTab2.MBRCity, tblHalfTab2.MRBState, tblHalfTab2.MBRZip, tblHalfTab2.MBRDrug, tblHalfTab2.MDLast, tblHalfTab2.MDFirst, tblHalfTab1.Field2, tblHalfTab2.MemberContacted
FROM tblHalfTab2 INNER JOIN tblHalfTab1 ON tblHalfTab2.MBRDrug = tblHalfTab1.Field1;
I'm not sure if that changes anything or not. Sometimes, it's just one tiny thing that can throw off the whole program. Sucks. Also, the field most likely to initially suggest a duplicate exists is the (MemberNum) field. Each member has his or her own ID number. However, they may be taking more than one medication, so the second field that would prove it's a duplicate is the (MBRDrug), so that if both the (MemberNum) field and the (MBRDrug) field are identical for more than one record, then it's safe to assume that he or she has already been contacted and can be removed from the list. I had included (MBRLast) as a further indicator, but it's not totally necessary, more for the user's information than anything else. Thank you so much for your help. I've gotten much further already than I thought I would. Hopefully I can get this silly duplicate thing ironed out and be good to go!