Alfred,
If you want someone not to open the tables from outside the app, the only way that I know of would be to include the DBC within the EXE. This is valid for small projects only... because in complex ones you might have to alter the DBC at runtime.
If you want someone not to alter your data but eventually see it, you might include a call to a specific function in the default value of your fields, something like:
GoApp.Check() AND
If you want someone not to read specific fields, you'll have to resort to encryption.
José
>Good morning to all.
>
>I remember reading somewhere that we can prevent a user that knows VFP from opening tables at the FVP prompt by defining an object variable at de DBC level and checking for it's existance before opening the individual tables.
>
>Would some one please guide as to when and where should this oVariable be and how to use it?
>
>Or is someone has a better way of doing this I'll appreciate the input.
>
>
>Thanx
>Alfred
