btw, adding userlevel is also quite easy..
I would make a seperate table for userlevels:
[userlevel_id] (autonumber)
[userlevel_title] (varchar(50))
etc. etc.
eg. if your different userlevels has different properties, as how much data they can store, you might add:
userlevel_storage_amount (int)
Then you want a 1:many relation on the users table and the userlevel table, so the fk would be a field "userlevel_id_id_userlevel_id" or something ,in the users table..
You would then generate a view in the access db and instead of running a query on a table, you run the query on the view.
You would also have to code in your application what the diffent users would be able to acces..
I would also store the login userlevel and username (not password) in global variables.
If using md5, etc. in the password, for "encryption", you also have to implement that on the password, before sending to the db for auth.
I'm not sure if Access has an md5 function.
Olav Alexander Mjelde
Admin & Webmaster