Active Query Builder support area

MySQL 64x Active Query Builder breaks

Avatar
  • updated
  • Completed

I am trying to implement the latest version of Active Query Builder WinForms .NET version and it crashes when trying to connect to a MySQL in 64x, is this a bug or am I missing something? It works fine with MySQL in 32x.

Avatar
Andrey Zavyalov, PM

I just checked the latest x64 Oracle ODBC driver (+OdbcMetadataProvider +OracleSyntaxProvider) and it works fine. Please note - because Oracle ODBC driver is platform-specific, you should specify x64 cpu architecture for your application.

If this is not the issue you encountered, please tell me details (at least error messages).

Avatar
Hannah Keller

Thanks, the latest MySQL driver worked. Is Oracle 11g Release 2 supported with the latest Active Query Builder? I am again running into an issue trying to connect on the Oracle 64x driver using an ODBC metadataprovider and an OracleSyntaxProvider.

Avatar
Andrey Zavyalov, PM

I tested the latest MySql ODBC x64 driver v5.2.5, and it works fine.

I used ODBCMetadataProvider and OdbcConnection with the following connection string:

"Driver={MySQL ODBC 5.2w Driver};Server=192.168.0.80;Database=sakila;User=root;Password=***;Option=3;"

Could you please test your issue using the latest ODBC driver?

Avatar
Hannah Keller

Thanks for your response. I apologize, I realized I should have been more specific with the issue I am seeing. I am using the Active Query Builder v2.4.6.587, MySQL ODBC Driver v.5.01.04.00 (64x), and setting the SyntaxProvider to MySQLSyntaxProvider. I am continually receiving the error: "Arithmetic operation resulted in an overflow". Let me know if this helps clarify things and whether you are able to reproduce the issue.


Thanks again

Avatar
Andrey Zavyalov, PM

Unfortunately, I cannot reproduce your issue.

I tested the latest Active Query Builder v2.4.6.587 with latest MySql .NET Connector v6.7.4 under Windows 7 x64,

and it successfully connects to MySql 5.5 on Windows 7 x32.

Maybe you encounter MySql Connector issue, which is already solved?

If you have additional information about your issue, please contact us.