Just switched to V4MD 3-d version, 2 problems

[Alexey Starchikhin]

Yes, it worked on V1. I'm surprised by the fact that you're surprised. :)

But  db.IOEncoding = "Win-1251" leads to empty fields instead of all
text,  and i can't find anything about it in the docs. :(

Alexey

On 14/11/07 7:58 PM, "Alexey Starchikhin" <ssa at sevenrays.ru> wrote:

>  2) When i at last was able to write data, another problem appears.
> 
>  This:
> 
>  AddRecord(pCursor, propertyListOfValues)
> 
>  works fine, but all russian letters is corrupted. :(  The same code
>  worked fine with V1, where Valentina engine succesfully converted
>  Director ANSI encoding into internal database unicode, but now, with
>  V3, it doesn't work.
> 
>  Can you advice me, how to solve this?

v1 did work with Russian text in V4MD  ????????????????

This is big news for me. I was sure that Director supports only ROMAN
languages...well at least if think about cross-platform move.


Please try in v3 specify also

    db.IOEncoding = "Win-1251"

For correct syntax please check docs.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc