We do it this way also. The only problem we ever ran into was using higher ascii characters in the original FPD26 app and then switching to VFP and windows codepages and pulling the data--yuck! What a mess it was for awhile!

Tracy

>Hi Mat,
>
>I was having similar problems saving encrypted information to a PostgreSQL database. What I ended up doing was running it thru a routine that converted each character to its ASCII value and then doing the reverse when I extracted the information from the database.
>Eg "065:066:067:" = "ABC". Simple but effective.
>
>Regards,
>
>Liam
>
>
>
>
>
>>Jos,
>>
>>You are right, the binary memo does work correctly, so the null character is causing an end of string. I was trying to avoid memo, but I may not have a choice?
>>
>>I also need to store this in a SQL database, I will have to test the field types there. Thanks for your help and quick replies.
>>
>>Kind Regards,
>>
>>Mat
>>
>>>Mat,
>>>
>>>It would appear that VFP is treating the CHR(0) as the null character - end of string terminator? I am not sure what you can do then? Have you tried the binary memo field or does that cause its own set of problems?
>>>
>>>Jos
>>>