Bob, Chris, etc,

Perhaps just storing the field(s) in question as Int would be cipher enough? Sure would exempt the DOS TYPE command from being a problem.

Cheers,
Jim N

>>>>I have a Human Resources VP who is paranoid about transaction
>>>>tables on a server. He wants me to write data in a system
>>>>(that is already running) with ciphers coded into the source
>>>>(eg multipling all salaries by .93331 when writing and by
>>>> some corresponding figure when displaying).
>>>>
>>>>I think doing this is begging for a disaster. Is there any
>>>>way to protect tables from a rogue with a VPF cd?
>>>>
>>>>Chris
>>>
>>>
>>>Here's a thought.
>>>
>>>Include the DBC in the application file and DELETE it from the user accessible data directory. (Keep a copy in you development directory of course). Now, the tables should only be accessible when opened from within the application. Even someone with VFP may not be able to open the tables because they can't find the DBC!
>>>
>>>Bob
>>
>>
>>OK...Here's one for you. go to a DOS prompt and TYPE table.dbf, where table.dbf is any dbf that belongs to a DBC.....WOW!!! I can read the data.
>>
>>Craig
>
>
>I guess this is one of the big reasons for the slow demise of DBF type databases. There is no trust left in the world (sniff! sniff!) Everyone wants 'secure' data (so they can look at it and no one else can!) I am reminded of a thought that I find handy from time to time:
>
> A wise man knows as much as he ought to, not as much as he can.
>
>But then, who is that going to stop, eh?
>
>Bob