>>>
>>>1) How many sites are you talking about?
>>>
>>>2) How much time would coding field level encryption/decryption take i.e. this becomes a money question.
>>>
>>>3) How big is the data file that needs to be encrypted? i.e. the file that holds the sensitive data.
>>
>>Why those questions?
>>
>>Do you have something to suggest depinding on the answers given?
>
>Obviously otherwise why would I ask them ...
>
>>Number of sites is not important.
>
>It sure is important - a few sites means certain 3rd party products become possible options. Many sites and that may not be viable or simply more costly.
>
>>Customers need it and they will get it. Time needed shouldn't be that big a deal. It's just a small percentage of data that will be encrypted. Data is not very big.
>
>If the data is just a few fields then Chilkat will do the trick. If the data file is small then you could consider encrypting the entire table, decrypt to memory and convert to memory cursor. Use the memory cursor during the session and save back as encrypted disk file. Or decrypt to "hidden" location, us in hidden location, and re-save as encrypted file when session ends.
>
>If just a few fields then encrypt fields and save to character binary fields. Decrypt on the fly when the record is required.

Thanks Jos.