[the_wizzkid]

Great, Shadow!

this resolved the problem, also the copying is fine now.

I'm just wondering- why does it function with a new installation of sqlyog 4.0.1 and when I update to the v4.06 RC1, it's gone? is there a kind of reset.. hmmm..

Thanks to both for your help.

[the_wizzkid]

Now I saw it, but it doesn't say anything about wanting to save the query, if you close it… Or did I read too fast?

[the_wizzkid]

Thank you peterlaursen,

I'm running 4.19 My sql Server.

Haven't changed anything on the server, only changed Sql yog.

The data in the Database is with Ü,ß etc. and I can see them correctly using my ERP system.

The Import has nothing to do with it, as I still have the correct data in the Database:

here is the output from Sqlyog:

00 01 D 010008 D Hübner-Kuhlmann

00 01 D 010009 D Unverwerth

00 01 D 010010 D Rummel

00 01 D 010012 D Scholtz

00 01 D 010013 D Außerer

00 01 D 010014 D Röhling/Richter/Schnitzer

with the earlier Version of Sql Yog – 4.01, the output is correct. ( I just tried it from another computer)

here is the output from our ERP system:

01 D 010008 1200 false AKTV EUR true Hübner-Kuhlmann

01 D 010009 1200 false AKTV EUR true Unverwerth

01 D 010010 1200 false AKTV EUR true Rummel

01 D 010012 1200 false AKTV EUR true Scholtz

01 D 010013 1200 false AKTV EUR true Außerer

01 D 010014 1200 false AKTV EUR true Röhling/Richter/Schnitzer

after doing a table copy, I see these caracters in the ERP system, too…

so they aer gettig altered during the copy. (I get the same effect if I do a mysqldump without the parameters: –default-character-set = latin1

Somthing changed with the characterset between SQLyog versions 4.01 and the newest one…

[Author]

Posts