Mysql / MS Cursor Engine Error

[Dmazzella]

I'm evaluating EA 3.5 Corporate Edition, connecting to a mysql (4.0.5) on a Linux Box.  I'm able to create objects and update them correctly, however there is an error being generated that comes up quite often...  

I can reproduce it via the following method (but it's not the only way to get it)
Create a new diagram,  add 2 objects, move one of them, hit Save.

The following error message pops up  a few times
"Microsoft Cursor Engine  [-2147217864]
Row cannbot be located for updating. Somve values may have been changed since it was last read"

Then a RunTime Error comes up, the application terminates.

When I open it up again, diagram opens up correctly.  

A quick google search for the error turned up this:  "Don't forget to pass to the list your exact table definition."

I submitted a bug report.  We'd really like to use this software, and this is the largest sumbling block in our way right now.

[gsparks]

Hi,

I have done some research and have the following suggestion.

In the ODBC configuration dialog for Windows/MySQL ODBC 3.51, there is an additional page of options which is accessed from a button marked "Options>>" at the bottom of the main
DSN setup.

Go to this options page and make sure the second option "Return Matching Rows" is ticked. Press OK, close the dialog and restart EA. Toggling this option on and off will cause the problem you describe as it determines how the driver access new rows during an update.


Let me know how it goes,

Geoff Sparks