Member Number - I havent imported yet.

Curious.

I havent done an import yet,
but do all members + 1 ?

I'm a classic user and I am Member Number 1(First Registration).
But in my test forum i am Member Number 2 (First Registration).

When i perform a import from classic to v7
will i be Member Number 2 and everyone else +1

Or will all Member Numbers rename the same?

Thanks for your replies.

Yeah, member #1 in .threads is reserved in the database for the placeholder/anonymous user. So, if you're #1 in classic you'll be #2 when importing.

and so on unless some members have been deleted over time in classic, then those behind them will move up - my number at UBBDev moved up about 110 places with the import to threads 7

I don't think I've ever complained about anything, but man that kind of stinks.

No way around that if I'm member 1 & 2?

Can I display a custom user number (1) field on my posts, even though it's really #2 in the database?

User 1 in threads has always been reserved as Rick said - why is this so bad?

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.

It is possible to change the importer so that all unique user-, post-, etc... IDs stay the same (maybe except for user #1 if you come from classic). That's what I did, because the way the importer works by default was not acceptable for me. Like you said, a unique database key has to stay unique forever, even after an import.