>Hi Cetin,
>
>The data in particular is sensitive in that if it were leaked to the public, someone would be able to see that "so and so is receiving x dollars per month" in payment. The person's address and phone etc information is already encrypted so not that high of a probability that anyone would be able to track down the person but this company has decided that if there were a data breach, they just don't want anyone to know how much the person is receiving - it's more being able to report that "all sensitive information" is encrypted to the privacy authorities.
>
>At the form level, yes it does not take any time to decrypt/encrypt. Where the slowdown comes in is for all their reports where this number is used for sales purposes, that I now have to decrypt that column of data for a bunch of records (they do some reports showing 5 year trends etc). All do-able and maybe not that slow but will have to test. I have already warned them of this and they are willing to wait longer for the data to be chugged through if decrypting.
>
>So yes, will probably just convert to string and encrypt. In that way, it is consistent within the app so that the next guy who comes along to maintain this will not be staring at some really weird field.
>
>Thanks,
>Albert

For reporting there wouldn't be any slowdown. You would get the data as encrypted so it takes the same amount of time that it takes now. You would do the decryption while reporting and a human isn't capable of noticing the additional milliseconds added per row.