Robin,

If a user has physical access to the machine or network which holds the files, i.e. they can actually open them directly, you can do nothing. Probably the safest solution would be to provide only a web based interface (eg an intranet or extranet) to the data stored in the DBF files. The web interface will dictate what data can be retrieved and accessed. Of course, whatever data is allowed to be accessed by the interface will be able to be dumped into another database or file and taken away by the user. But at least the interface will only provide that data which you program it to allow.


>Hi
>
>I've been asked by my customer to add the facility to allow another machine to access their application in the same office, and allow the user to edit certain details in a table.
>
>However, the user will be quite computer literate and they are concerned that he will be able to access/copy the DBFs and take them away with him.
>
>How can I make the data only accesable via the software?
>
>I seem to remember there was a trick you could with the database container to stop the dbfs from being opened without 1st correctly opening the database?
>
>Is a third party product probably best? As usual the customer does not want to spend a lot of money on this.
>
>I'm not using SQL! I selected it by mistake.
>
>Thx in advance