So you are dong this check against data with the proper name already known? Why bother to clean up the name when all you need is the ID?
Sorry for my confusion.
-Bill
---In MS_Access_Professionals@yahoogroups.com, <jan.hertzsch@gmail.com> wrote :
Thinking about it, my problem is less complex than I first thought. Regardless of the nickname (Bill, Billy, Willy) I want them to come up with the "proper" first name (William). So my crosswalk table has several sources to one target.
Bill>WilliamBilly>WilliamWilly>WilliamI create a query that selects only the records from my Patrons which have a blank in the VOTER_ID field and use that to create a new table (Temp_Voter_Match?) using the same prime key as the Patrons table.I do an update query to on Temp_Voter_Match table replace the nickname with the "proper" name.I run theTemp_Voter_Match table against the Voter Registration table now matching "proper" first name plus last name and updating the Voter_ID field with any hitsFinally, I update the VOTER_ID field in my PATRONS table using Temp_Voter_Match table. Since they have the same primary key, it should be easy to match.I have not tried this yet but I think it will work. I just have to overwrite the Temp_Voter_Match table every time.Comments?
__._,_.___
Posted by: wrmosca@comcast.net
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar