Hi Paul!
Thank you for your suggestion. My concern is that using an INNER JOIN will require one field to definitely match, instead of using a looser structure... I know this should not be a problem with proper primary keys in place, but I have inherited this database where the data is not all standardized and don't always trust the fields to match up when they -should- (which is actually the reason I am checking all of these three fields - which all "should" be the same... but for accuracy's sake I wanted to find them all).
I am trying to go through and standardize everything, but in the mean time I fear that fields may be falsely excluded using the INNER JOIN in this case, unfortunately - is that correct?
For example, if I choose to INNER JOIN ON the .QPP field, that is fine and everything is perfect if all the QPP's match up (it will correctly select records with the other two fields). However if there is an issue with the QPP field, that record would be mis-handled. Is that correct thinking?
If that is the best way to go, I will do it, but I just wanted to resolve that feeling I have that something could go possibly awry with the data I currently find myself with...
Thank you again for your suggestion!