>OK - I know - I should use an SQL server and the security which it provides.. but not everyone can afford SQL server.. what I need to do is encrypt the data in the dbf/fpt files - so they can't be opened using foxpro or access etc. Does anyone know of any third party controls which can achieve this?
>
>Thanks for your time..
>
>Andy.

Using encryption algorithm's do not make dbf's read-only 'so they can't be opened using foxpro or access etc'. They will simply make the data unreadable when the tables are opened in one of these environments. And if the data is changed without going throught the encryption engine, the data could be lost completely.

You really need to take a look at other options if SQL Server is not feasible. You could place the data on a server and use a middle tier com object to access it, etc.

Perhaps you need to take a real close look at the costs of SQL Server versus the expense you could incur if data is mistakenly changed in fox or access - and the costs you would have to repair that data.

HTH