There's not much you can do to actually stop the viewing of information in a dbf - especially fp2.x. The best you can do is rewrite the code that stores the data in the fields to encrypt it so when someone does view it in fp, etc - all they see is (what looks like) garbage.

The link Sergey provided gives you a good start for an encryption library - or the client create their own.

-w-

>Hi all,
>
>Been a looong while since I've been on here. I've been very busy and hope you'll forgive me.
>
>I've been asked here at work what can be done to protect credit card numbers in the Foxpro databases. I'm pretty sure they're using Fox 2.6 for DOS, if that helps. What advice can I give them to modify their databases to protect them from unauthorized users viewing the data? Particularly if it means not having to change the code (which I haven't seen) but if they have to change the code, that's just what they'll maybe have to do.
>
>Any help you can give would be greatly appreciated.