Then Avisshek you will have to tell (or advise) your client that they need to use a formal CMS or LMS if they wish for a secure log in.
If an insecure log in is required then you will find some suitable html or java based options freely available. However if on a CD anyone will be able to get around them and access the content.
For CD based content it is not easily possible.
For web based content you'll preferably need a database to store the user names in, then use PHP or Java to validate a user against the database.
An hta file of users will work but it is a little clunky. There are commercial code generators for this. If it is to apply to individual modules then you will need many and it becomes hard to manage...
Get your client to define exactly what they want and ask again.
Then Avisshek you will have to tell (or advise) your client that they need to use a formal CMS or LMS if they wish for a secure log in.
If an insecure log in is required then you will find some suitable html or java based options freely available. However if on a CD anyone will be able to get around them and access the content.
For CD based content it is not easily possible.
For web based content you'll preferably need a database to store the user names in, then use PHP or Java to validate a user against the database.
An hta file of users will work but it is a little clunky. There are commercial code generators for this. If it is to apply to individual modules then you will need many and it becomes hard to manage...
Get your client to define exactly what they want and ask again.