>How can I do so that a .DBF can not be read
>and written by no aplication besides
>my .EXE ?
>
>(I mean: only my EXE could change the table)

Four thoughts:

1) Use an extension other than DBF. This will fool applications that don't have too clever a person behind them, and it's super easy to accomplish.

2) Encode the data within. There was an article aeons ago in FoxPro Advisor that showed how to encode data when writing to the DBF, and decoding it upin reading it. There also used to be some add-ons that kinda did this, but I never heard reports on their reliability.

3) Intentionally corrupt the header upon exiting the program (using low level file commands) and fix it upon starting the program.

4) Zip the files into an encrypted zip file upon shutdown, unzip upon startup.

The first two methods will provide protection at all times. The last two will have data accessible while the program is running, and may be difficult to manage in a network environment.

FWIW