This is a really odd problem. We're setting up a new server with SQL 2000. [v 8.00.818 (SP3)] The first time it was installed, we chose the authentication method to be "Windows Only". We then uninstalled it and re-installed it using "Mixed Mode (Windows and SQL Authentication)" I don't know if that's what caused this problem but it may be relevant.
The problem occurs in the "SQL Server Login Properties" dialog box. To get to that dialog box, open a server in the tree, expand "Security" and then click on "Logins". Double-click on a user in the list. The window that opens is the one I'm talking about. What happens is when I click on "OK" to close the window, it pops up the "Confirm Password" box, requiring me to confirm the "new" password before I can close the user's Properties. When I enter the correct password, it says "The confirmation password is not correct." I have to then go back to the "General" tab and enter the password there, click OK and then re-enter the password before I can save changes to the login's properties!
I develop windows applications myself so I suspect the bug is that when the Properties dialog box is initially shown, the value of the "password" variable is wrongly initialized. Then, when the user clicks "OK" the system compares the value of the password in the form with the one currently assigned to the user and detects they're different. It assumes the user has entered a new password in the form and prompts for them to re-enter it.
Has anyone heard of this kind of thing happening before? It's so obscure! It just frustrates me even more with SQL Enterprise Manager. It's good for some things but in other ways it can be quite erratic and I fear this might be another example of that. As I mentioned, this is a fresh install of SQL and I really don't want any quirky glitches floating around and I'd much rather kill them off right from the outset. Re-installing didn't fix it, though.