[solved] Windows 32 / 64 problem with TWideStringField

[cfc]

Hi Michael,

All taxes well until you run the program in Windows 32. The machine on which work is Windows 7 64 and varchar fields are read as TWideStringField, but when the same program compiled on my machine I run it on XP 32 or Windows 2003 Server, varchar fields are read as TStringField.

Greetings.

[EgonHugeist]

cfc,

imbelievable for me. About which protocol do we talk now? Zeos-Egonhugeist does decide which FieldType is needed on the client-characterset. If this an encoded one then the TWideStringField is correct. If this one is an Ansi encoded one then the TStringField is choosen.

Question did you set the TZConnection.ClientCodePage? If not then Zeos has an different behavior if your engine default encoding differs...

But i can not believe that this issue has dependencies to the 32/64Bit environment.

Michael

[cfc]

Michael,

Excuse me, you're right, the problem was the Oracle client configuration on each machine, by setting in ZConnection clientcodepage UTF8 works perfect regardless of how this set NSL_LANG.

Thank you very much.

cfc.

[EgonHugeist]

cfc,

thank you for repley. Case closed...

Michael