>Wayne,
>
>To clarify my earlier question -
>
>My customer was planning to have one password, the same password for all his users. So I don't think it needs to be stored on a server. All I am doing is making it so that when a user enters the common password they can get to a web page and view it only. The web page is a calendar that shows my customer's meeting schedule.
>
>I plan to imbed the JavaScript into the HTML on the Enter Password web page. If they enter the correct password I would go to the meeting schedule calendars web page. If they enter an incorrect password I would display an error message and let them try again. In this case, I might not need a program running on the host server? Is that correct?
>
>My customer is not very concerned about others seeing his calendar, so the security issue is not very important. This is lite security I guess you could say. Thanks again.

You might be better off to use a basic authentication.