>>Is there a way to avoid access to a 'dbf' from another
>>application, like and editor, how can I control the
>>fact that somebody with a local copy of foxpro in a local drive can 'Browse' any table ?. Is there a way to avoid that, do I need to move to 'SQL Server' to have that control, I would like to have something like a 'password' to browse a table, and I am afraid to use encription. Any sugestion will be apreciated.
>
>Encryption might be a solution.

If U are using the database container; U could create a stored procedure that is called via the table trigger properties. I created routines to prohibit editing of records marked for deletion, recall of children records if a parent is marked for deletion and other stuff. I also have a database which contains table names and menu options (Add, Edit, Delete) along with a user level. I imagine U can create your own routines to determine if the application is being used to access the data. Either set a global flag in the main program and if the flag is not defined or invalid; then no updates to the data. Without knowing more, U are limited with DBFs. SQL Server is better at the level of security U are looking for... just some early morning thoughts... Steve