Bug #7867 Cannot export shapes from Visio 2003
Submitted: 13 Jan 2005 11:01 Modified: 24 Mar 2005 4:56
Reporter: Ole Poulsen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.8 OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

[13 Jan 2005 11:01] Ole Poulsen
Description:
I need to export properties from Visio drawings to a MySQL database.
I use the Tools -> Add-ons -> Visio Extras -> Database Export Wizard function to export custom properties from the Visio drawing using MyODBC-3.51.10 connection.

When I run the export 2 things happen:
1) the requested table is created (and replaced if it exists)
2) I get an errormessage "Failed to export data to external database" (from Visio)and no data rows are added to the table.

The expected result was that the table should be created and populated with data from the shape properties of the Visio drawing.

The problem began when I got a new pc and installed the MySQL version 4.1.8.
My old pc was installed with MySQL version 4.0.10-gamma.
I examined the old pc setup and found that two flags were ticked in the ODBC connector setup:  "Don't Optimize Column Width"  and "Return Matching Rows".
Checking these two flags did not fix the problem.

I tried to install MySQL version 4.0.23 but the same error happened.

I installed MySQL version 4.0.10-gamma (as on my old pc) and it worked as expected!

How to repeat:
1) Create a new ODBC connection to a (dummy) MySQL database. Choose root as user and correct password.
2) Create a drawing in Visio 2003 and insert any shape from a stencil.
3) Optional:   Update the shape with one or more Custom Properties.
4) Run the Tools -> Export To Database
5) Select your ODBC data source and enter a table name
6) press 'OK'
[19 Jan 2005 18:45] Jorge del Conde
Verified using Visio 2003 trial
[24 Mar 2005 4:56] Jorge del Conde
Hi!

I wasn't able to reproduce this bug using 4.1.11 from bk & myodbc 3.51.11
[24 Mar 2005 4:56] Jorge del Conde
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/