>>>Encryption might be a solution.
>>
>>Also, if you have dbc, it's good to have some update/insert/deletetriggers using custom app properties, so nobody could change data outside the system.
>
>I like that idea, Edward, but lets say that I decide to go with
>the encryption, and something happens, i.e. a corrupted dbc, or
>dbf, am I going to be able to fix the Encrypted data ?

Encryption is a gamble in my mind. I would not do it unless the client (internal or extrernal) was well aware of the possible implications. If you have a limited budget and can not afford a real dbms that can support security like oracle or sql server, then encrytion is a possible solution. Please make sure that you have a very good backup scheme in place to cover the possible problems that you mentioned. Lossing one day of data is worst case scenario that I could live with, but what about the users? htwh. Steve