MDG Office 64-bit and MySQL ODBC DataSource

[iblocks-shaun]

I am trying to use the 64-bit MDG integration for Office. Our EA repo is stored in a shared MySQL database. I setup a MySQL 64-bit ODBC DSN using the MySQL ODBC/Connector (version 5.3.7 - https://dev.mysql.com/downloads/connector/odbc/).

I created and saved a Word document. I clicked "Connect to Server". On the Data Link Propeties Windows, I selected "Microsoft OLE DB Provider for ODBC Drivers" on the Provider tab, and on the connection tab I selected my DSN, entered my DB credentials and selected the initial catalog to use. I also clicked the Test Connection button, and the test succeeded. I clicked the OK button, and a message dialog appeared with the title "Connecting to EA Repository" and a message "Please Wait." After a few moments, a separate dialog appeared with a message "Connection no successful". I have tried both an ANSI and a Unicode DSN, with no success.

In Enterprise Architect, we have used a MySQL 32-bit ODBC DSN successfully.

Anyone have any idea why the MDG Integration for Office is not working? Have I done something incorrectly? Is this something to do with it being 64-bit?

[Eve]

You still need to use the 32 bit ODBC driver. The EA API is called, and EA talks to the database.

[iblocks-shaun]

After some trial and error, I managed to construct a connection string for a file-based 32-bit file DSN. The 32-bit system DSN was not appearing in the list, I suspect because I am using a 64-bit version of Word. The connection string is as follows (actual parameters masked with ****):
Driver=MySQL ODBC 5.3 Unicode Driver;SERVER=********;UID=********;PWD=********;DATABASE=********;PORT=3306

However, I am now getting the following error message:
The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Provider for ODBC (System.Data.Odbc)

Any ideas on how to resolve this?


Edit: Just for additional information, I am using Office 2016 on Windows 10, as well as Enterprise Architect 13.

Edit again: I found this page describing the error message (https://support.microsoft.com/en-us/help/310374/error-message-when-you-try-to-use-the-oledbconnection.open-method-the-.net-data-ole-db-provider-system.data.oledb-does-not-support-the-msdasql-provider,-microsoft-ole-db-provider-for-odbc-drivers.). Is this helpful? Is it possible for me to resolve my issue without a code change to and release of the MDG Office integration extension?

[iblocks-shaun]

After multiple attempts, I cannot find any way to use a 32-bit ODBC DSN with Word 64-bit. Either I am building my connection string incorrectly, or the extension requires a 64-bit DSN and the EA API requires a 32-bit one (and thus they are in conflict). As the extension is essentially a black box, I cannot ascertain which it is.

I am currently evaluating this MDG Integration for Office for use in our organisation. At this time, I cannot recommend this extension, as it does not seem possible to use it with Office 64-bit as far as I can tell (despite the indicated support for 64-bit Office applications). This is disappointing, as it would greatly simplify our creation of specifications for clients.

I would appreciate any assistance with the above problem?

[Geert Bellekens]

I would appreciate any assistance with the above problem?

I hope you do realize you are posting on the user forum.
If other users have had the same issues they might be tempted to help you out, but it you really need help with a specific problem you'll need to contact Sparx Support.

Geert

[iblocks-shaun]

I must apologise, Geert.

I did not realise that. I will direct any further queries to the Sparx Support email address. Sorry for any inconvenience.

For the sake of completeness. We have decided to go with the eaDocX extension as it better suits our needs.

[Geert Bellekens]

I must apologise, Geert.

I did not realise that. I will direct any further queries to the Sparx Support email address. Sorry for any inconvenience.

For the sake of completeness. We have decided to go with the eaDocX extension as it better suits our needs.

No apologies needed.

Just to be clear, the Office MDG and eaDocX are completely different types of products that have completely different use cases. I don't see how you could trade in one for the other (unless you misunderstood what the Office MDG promises to do)

Geert