Mike Nolan,
Would it be hard to add a check for duplicates within a membership batch? I submitted a batch of 49 memberships this weekend and after overridding several possible duplicate membership warnings where I could not figure out what was even similar, I submitted the batch and then found out that I had bought two memberships for the same person. This was cleared up on Monday but it would be nice to find out earlier.
Also, I had a mother of two players renew through the USCF membership store and she just bought new memberships instead of renewing. New IDs were issued even though the names and addresses were exact matches. Is there not a check when you buy membership through the store?
I know you have a lot to do and neither of these things is a big deal.
Mike Regan
Yes, we do try to catch duplicate names and addresses on the webstore, and we also do a nightly run to look for duplicates that slipped through anyway. PM me or drop me an email on those two, I will check to see why they weren’t caught.
The TD/A membership system really needs a rewrite. That was the first TD/A module I wrote, I’ve learned a few things since then and the USCF has changed since then as well. (For example, family memberships didn’t exist when I wrote that module in 2004, they were kind of grafted on, and could work a lot better.)
Checking for duplicates within a batch has not been a major issue so it isn’t very high on the list of needed fixes.
When it comes to programming, if you would do something now the same way you did it two years ago then that is a sign that your skills have possibly stagnated.
That depends, if the way it was done before does not need to be improved upon, then why change it, or for that matter why rewrite it? 
That’s why I limited the adjective to “possibly”.