Denis,

Was the memo field created as NOCPTRANS? ie a binary memo.

>Hi Sergey,
>Thanks for response,
>Well.... on which step this translation happen?
>I have CPCURRENT() 1252, CPDBF() 1252.
>and... when I do GATHER NAME - whats happen? loData properties change own codepage to 1251 and then replace field? because SAME value, SAME object when I did REPLACE - all works right..
>I agree about character/binary. but it seems in any case a bug here... or?
>
>Denis
>
>>You should use character/binary fields to avoid code page translations.
>>
>>>I using Cipher.FLL to encode string.
>>>I using next simple code for example
>>>

>>>SCATTER NAME loData MEMO BLANK
>>> loData.Field = ENCRYPT(string,password)
>>>APPEND BLANK
>>>GATHER NAME loData MEMO
>>>
>>>?ENCRYPT(field,password)  &&- return bad string, with unknown characters
>>>

>>>
>>>
>>>Then another way
>>>
>>>
>>>

>>>SCATTER NAME loData MEMO BLANK
>>> loData.Field = ENCRYPT(string,password)
>>>APPEND BLANK
>>>AMEMBERS(laMbr,loData)
>>>FOR lni=1 TO ALEN(laMbr,1)
>>>  lcPropName = laMbr[lni]
>>>  REPLACE &lcPropName WITH loData.&lcPropName
>>>ENDFOR
>>>
>>>?ENCRYPT(field,password) &&- return correct value
>>>

>>>
>>>Question: Is it well know bug when GATHER NAME wrong play with codepage when update field?
>>>