>>>>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)
>>>
>>>The only way to prevent the data from being accessed is to use a database server as your backend. SQL Server has built in application roles that will allow only your application to access the data.
>>
>>Not true; the Cryptor product addresses this exact issue.
>>
>>http://www.xitech-europe.co.uk/
>
> So encrypting the content of the files eliminates anyone from (1) changing that information, or (2) deleting the files alltogether? Data encryption is not complete database security and does not do what was posed by the creator of this thread "only my EXE could change the table".

Of course it doesn't prevent someone from corrupting or deleting the tables. It does prevent undetectable alterations to data, and it prevents the data from being read at all except within the context of the app. For many users, this is all the protection they need.

Perhaps the thread creator could clarify what was meant by "only my EXE could change the table".