Sure...but a big problem is that if you do it with a unique user name and a user tries one that is taken, they will be told and will have to choose another...fine...I choose another...if I look at the user list and see that user that is using my first choice for user name...hey, the program works!

Now, if you do it the other way, and you have unique passwords (and therefore can log on with only your password, and your user name will be found)...well, there are a few problems...like, John Smith is not the John Smith I was chatting with yesterday (see, I can tell the difference between John Smith and Johnny Smith and John C. Smith etc.)...and the big problem is when I choose a password and it says "That password is taken, try another."....BIG problem...now I can take a list of users and I know that one of those users are using that password...now I can eventually get into the site or network on some other user's account...in fact, the original idea was just to have a password to log on...great, now I just have to type in this password and I am logged on as this user...

Is this clear?

Joe

>> As long as you have two fields where one is unique. :)
>
>Thanks Michel. Had wanted to find out why for a long while already 'cause like what you'd said (above), I see no problem doing it the other way round.
>
>John Low.