Fort some unknown reason, I'm not able to export a table with the EBD Manager build in export function and its encoding setting of Auto. The description states, that it will use the encoding of the DB if it is set to Auto, but this seems not to be true. My Database/Session ist setup as ANSI, but an export does still genarate a unicode file. So I'm forced to set the encodeing manually to ANSI, which will work fine than.

Regards
Rolf

Rolf


Which version?

Roy Lambert

Rolf,

<< Fort some unknown reason, I'm not able to export a table with the EBD Manager build in export function and its encoding setting of Auto. The description states, that it will use the encoding of the DB if it is set to Auto, but this seems not to be true. My Database/Session ist setup as ANSI, but an export does still genarate a unicode file. So I'm forced to set the encodeing manually to ANSI, which will work fine than. >>

The manual states that it will use the encoding of the *engine*, but now that there's the Unicode/ANSI character set selection per session (as of 2.15), this is a little less clear.

In general, how it works right now is that it will use Unicode if the compiler is Unicode, and Ansi if the compiler is Ansi.  The EDB Manager is compiled with a Unicode compiler, so the EDB Manager defaults to using Unicode.

I'll make this a little more clear in the next build and have it use the session's encoding in the EDB Manager, but for now just be specific about which encoding you want and you'll be fine.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

Great! That's exactly what I did expect.

Thanks
Rolf