>>>>I actually do use a seed based on the PK value with additional "twist". So that even if someone has the table and knows the PK value, they would have to figure my "twist". And if they do, they deserve to have the data :)
>>>
>>>Well that changes matters. Without that, I have agreed with Cetin.
>>
>>My main concern now is where to store the encrypted field. Binary does not seem to be the option since, as John Ryan said, it could be a problem for the ODBC driver.
>
>Then go back to the beginning of the thread, when I said to add "Autotranslate=no;" to your connect string. No translation, no trouble with binaries going over the wire. This was battle tested with exactly the same kind of problem.
Never mind.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
