>I've already it implemented but i'd like to read more opinions about it.
>

>* I use this structure to save users:
>USERS.DBF
>   Username
>   Password
>* and this for save permissions
>PERMISSIONS.DBF
>   Id
>   Username
>   OptionD
>   OptionU
>

>In table USERS I save just the name and the password for each person who will acess the application.
>I have a relation (USERS 1 .. N PERMISSIONS) where I define what is the options and if it can be used (or not) for the Username.
>For example:
>Field OptionD - I store something like that:
>
>INSERT_CUSTOMERS: Can username include new customers? (S/N)
>ALTER_CUSTOMERS: Can username alter customer's data ? (S/N)
>DELETE_CUSTOMERS: Can username delete customer's data ? (S/N)
>and so on...
>
>I hope you understand my way to save user and acess. I'd like to know some other solution about it.
>
>Thanks in advice!

If that fit your needs, this is OK.
But, how do you protect the table from a browse by a user with VFP?