>Because any user with a copy of VFP can open the databse of my application and view or change data outside of the application, how can I implement a level of security to my application like including a password to my database.
>
>
>Thanks
>Carla
Carla,
There is no password option like in many other databases. This practically means you cannot prevent others opening your DBC. In fact passwording in others doesn't also mean you cannot open them (to open them you don't use their host language but something like an hexeditor - in theory every encryption could be solved especially if widely used). Other than that you could encrpyt/decrypt VFP data too. For that you could use a 3rd party such as Cryptor or write your own (check also cipher30, cipher50.fll in files section).
Except for viewing part you could also put another level of security to DBC via stored procs. ie: a stored proc could check existence of a var and its value to match your *password* and deny update in case of failure (table level validation would call it).
Your implementation of security would depend on how much hacking you expect. Also some security would be set at OS level.
Cetin