Hi David,

What data type are you using to store encrypted data in SQL Server? If it's char type or it's variation, it's value will be truncated at CHR(0). You should use binary or varbinary data type in this case.

>I am having trouble with encrypted fields. I am using MSSQL as my database, which I connect to across the internet and VFP7. I have some address fields which I've encrypted using the CryptoAPI RSA Base algorithm with a 26 character key which consists of characters such as "{2ú¶‘Аmt".
> The problem that I am having is that sometimes, depending on the position of the character and which character it is, the character and all following characters in the field are truncated. For example, in a first name field, once the first name is decrypted, it reads "Dav" instead of "David". What I do know is that it seems to be where a null character is used as the encrypted character. Would it be better to use a block cipher instead of a stream cipher? Has anyone ever had this issue before? I can't seem to find any info on it.
>
>Thanks,
>David