Everything was fine until chapter 12. When I came to page 406, I ran the code, I entered the password for user, manager and admin, password didn't work of course, because password is hashed in database previously, i guess in Chapter 11. I copied the hashed password and entered it as password in login form, and it worked. Actually, login form was one of the things that i was wondering most. I'm also using in my programs returning back userid if login succeeds, but what I was wondering how to compare the password in server side, i mean sending encrypted password over the network, decrypt it in stored password, hashing it and comparing with the database value. when i saw that password kept as hashed in database in the sample, i was amazed that i can see a nice example of such login procedure, but now i'm dissappointed after chapter 12. Now, until the end of the book, i need to use hashed string as a password to login :( Any suggestion? maybe an errata to stored procedure in chapter 12 (usp_ValidateLogin)?

Thx in advance

I'm not quite sure what the question is. Could you restate the question please?

Thearon

Simply, the passwords are hashed inthe database, but the password that we are entering in Time Tracker application and Web interface, are not converting the password to hash and send it to stored procedure, nor the stored procedure is getting the password, hash it and compare it. Therefore stored procedure compares the pure password with hashed password in the database, as a result, user cannot login. I'm copying the hashed password each time from the database and entering into the password text box in the application to login.

Please check step 11 on page 403. This is the procedure that calls the procedure to hash the password before calling the stored procedure.

Thearon