Robin,

In this case such stuff like normalisation with surrogate keys does a lot of work. It's not impossible to retirve but it makes it harder.

The problem is simple how serious the problem is. If there is a real need to protect the dataa DBF based system is wrong I think.

Agnes
>Hi Viv
>
>The user won't be VFP literate or a programmer for that matter, just know they way around Windows/Excel etc.
>
>>>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?
>>
>>Don't know of anything along those lines that someone who is Foxpro literate couldn't circumvent. There are two options worth exploring - (a) encrypting the database (b) restricting access to the windows data folder and impersonating a valid user in the VFP app.
>>
>>HTH,
>>Viv