XML import to MySQL database

[andlil]

Hi !

I have tried to migrate an old project from 3.11 into the new
beta using a MySQL database.

I upgraded the project with 3.50 and the I exported the
file to XML. I created a new database and tried to
import the XML file into the new database project.

After some time a dialog showed up with
[-2147217887] and the import failed.

Have anybody got the same problem ?

/Anders

[andlil]

Hi again !

I found another way of importing data using the transfer
tool.

It worked much better.

/Anders

[gsparks]

Hi Anders,

I believe any problems with the XMI import in EA 350 have now been ironed out for the final release.

In general though you should use the Data Transfer function to upgrade a .EAP file to MySQL or SQL Server. The reason being that the XMI file does not include such things as custom metafiles and images, project specific info and other basic data . XMI import expects a certain amount of backgournd information to be already present.


We also recommend you use the Data Integrity check before upgrading. Failed imports, network crashes and some other early bugs in EA can cause some 'dangling pointers' to diagram links, elements etc. Cleaning these up before upgrading is a good idea - although not essential.


If yuo still experience import problems with the latest build of EA 3.50 - please let us know - and a copy of the offending .xml file is always appreciated,

Cheers,
Geoff Sparks