heng a · Aug 7, 2018 go to post

Hello Eduard Lebedyuk,First of all, thank you for your answer.

Sorry, I forgot to say that I tried it before. But it doesn't seem to work either.

It should be noted that the file format of the local client is consistent with the expectations, but the server side seems to be affected by the difference.

Client:

 

While, the server side:

Thank you again for your help~

heng a · Aug 8, 2018 go to post

The operating system I am using now is win10 Pro. The original regional setting was China, and it was later changed to the United States. However, it still seems to have no effect.

Later, I found out that as long as the text file does not contain Chinese characters, such as "乱码", the file encoding format on the server side is normal, that is UTF-8. Otherwise, the file format is automatically saved to ANSI (very likely corresponding code page For 936 GBK).

I don't know if this involves the relevant settings or processing of the Chinese code for the operating system, and whether this information is enough to provide more clues or tips for everyone.
But still thank you.

heng a · Aug 8, 2018 go to post

Oops, a joke, I am sorry that I understood wrong before.

Configuration is like this:

heng a · Aug 8, 2018 go to post

That's right, this is the correct solution, sincerely thank you for your help!

wish you a happy life~smiley

heng a · Jun 20, 2022 go to post

Thanks for your sharing first. I have tried this example, but get this pic.

heng a · Jun 21, 2022 go to post

I just changed the path in the example.Make the 'tPath' consistent with my environment.

In addition,

USER>zw $zv
"Cache for Windows (x86-64) 2016.2.3 (Build 903_10_20040U) Wed Jul 1 2020 16:11:04 EDT"

heng a · Jun 24, 2022 go to post

Maybe it has been solved.Try to modify the output encoding, it should be working.

a:"WNSK\RAW\":10 e  "*ERROR* INVALID FILE"

heng a · Aug 10, 2023 go to post

just the second classmethod ,name “odbcTest”,SqlName=“PersonSets2”