Thanks...I will take a look. In this app, the only sensitive info is some limited bank account info - name and account number - so the client probably only needs two fields in one table encrypted. And even in that case, I am having a hard time convincing them that it is worth their while to do so - they don't have data on the road and they have a so-called "good" firewall (as good as it gets) but I still think they should encrypt this - just in case someone, somehow gets in (or an employee copies the file). And they have said "even if someone gets the file, what can they do with it - it is just a name and a bank account number - they still would need ID to do anything with that account). My thought is that it would still be a public relations nightmare even if it is not that useful.

Albert

>i've used Cryptor in the past and it works great.
>
>It encrypts the entire .dbf file.
>
>http://fox.wikis.com/wc.dll?Wiki~Cryptor~VFP
>
>good luck,
>Dave.