[Néo]

Hi there,

is the problem described above considered as fixed ?

Just wondering whether the problem I had importing from DBF Files was on my side, coming from my Foxpro ODBC Driver or something you'd get fixed in SQLyog.

Thank's for your help

Néo

[Néo]

All right, I'll do that as soon as I get back to my office…

[Néo]

Well, I first imported the data with SQLyog BEFORE trying to index the tables and only then discovered it had created duplicatas.

I tryed the same exercise AFTER having created the indexes and SQLyog then reports me errors, so some of the rows can't be imported.

I used PhpMyAdmin to create the primary indexes since it appeared simplier to me in case of multiple fields primary key creation.

By the way, that kind of errors worries me a bit concerning the data integrity, huh ?

Thank's for your help

[Néo]

Well, no, I don't create the XML File manually but save it from a “manual” replication (not a scheduled one).

[Néo]

Well, I was about to ask the same question !

Additionally, if there where any feature to schedule this import, my replication problems would be totally rid off.

C'mon guys ! you're just so close to the ultimate replication solution !

[Néo]

Shadow

well, I finally found a solution : I create the sync. XML file manually and then use it in a DOS batch file to shedule it. Assuming your job file is named “sync.xml” and your Batch file “Sync.bat”, it would more or less look like this :

cd “C:Program FilesSQLyog”

sja “C:your_pathsync.xml”

and it actually works well !

Thanks anyway

Neo

[Author]

Posts