>I found out that besides protecting table from being open, I can also prevent the .dbc from being opened by
>coding PROCEDURE dbc_OpenData
>
>So I think user can only open .dbc using a text editor and not by VFP anymore
>
>The question is
>
>Will the use be able to remove the code from .dbc internal procedure with a text editor, without causing damage to it ?
>
>
>Moises

A thing you could do is implement a checksum for all the fields in a record. That way if a user modifies the data outside the application you'll be able to verify it when you launch the application.