>>>How do you convert a VFP string to a base64 encoded version?
>
>You might consider saving time and $ by simply using VFP's STRCONV with nConversionsetting =16, then 15 to restore. One line of code, no other dependencies.
I will consider it.
What is strange (to me) is that despite the insistence of gurus here that non-printable characters cannot be saved into a Char() field of SQL Server, I have not came across a problem. I have a number of customers who store my encrypted string (with many unprintable characters) in the Char(250) field and I have not seen one issue.
What I will do is connect to all of these customers and do another test. Simple get the value stored in the Char(250) from SQL Server (with many if not all unprintable characters), then on the VFP side run them through the cipher() function and see the results.
"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
