MySQL connectivity needs to be updated.

[john w]

There appears to be a difference in the way InDe connects in the IDE and at runtime for MySQL. The connections test successful in the IDE and show data but fail at run time.

[lucabaldini]

"Unfortunately" that's correct... :-|

The IDE is a C++ app that uses OleDB (for Access, Oracle 8+ (OraOleDB) and SQL Server) and other ODBC (Oracle 7, ODBC, DB2, MySQL, Postgres, SQLite) connections when connecting with databases. That's the only way we can use to connect from a Windows' C++ app to any database. You install the OleDB or ODBC (depending on the database) driver and IDE can use it.

At run-time things changes... The system uses native (C# connector or Java) connector depending on the language you choose. Again, there is not much that can be done here... Instant Developer produces a C#/Java solution... so if I need to connect to a database I have to do it using C#/Java.

There is not much I can do for that... As I say "world is too complicated"... :-|

[john w]

There also seems to be a versioning issue with MySQL. It would be nice to use current versions of the ODBC and .NET connector. The security process changed in the newer releases. It seems like that would be a worthwhile thing to use.

Jack helped me with the problem and explains this issue better than I did . viewtopic.php?f=7&t=91460

[lucabaldini]

Jack did an excellent job... I've created a ticket for the other thread so that I can fix it and distribute the latest driver for MySQL (as I did it for Postgres some time ago).

For the ODBC part I can't do much... The IDE will use the first ODBC driver for MySQL that is available on the system... if more than one is installed that's a pain... normally a new version of the database will uninstall the old ODBC driver and install a new one... if, and only if, during database installation (or update) the "install/update ODBC driver" is checked as well...