It sucks because it is an identifying attribute that "should" be treated as ALWAYS UNIQUE and can not be changed.
I've been through 3 upgrades now and each time all member numbers have changed causing me to have to modify remote scripts.
I really think you should rethink the methodology of the MEMBER number and prevent it from changing. How many other production type databases can you think of where the User/Member ID changes with updates? Sorry, but I can't think of any. Every DB update I've ever done did not modify the data like this software does.
