MySQL trigger to insert to MS SQL Server 2008 ?? (no replies)

February 2, 2016, 11:25 am

≫ Next: MySQL and Javascript at client (1 reply)

≪ Previous: Remote connection to MySQL (13 replies)

$

0

0

I need to insert/update two tables in an MS SQL Server 2008 database when a row is added to a MySQL database.

Can I do this? If so, how?

I assumed this would be relatively easy but I can find very little information on it.

Thanks for any suggestions.
Ron

---

MySQL and Javascript at client (1 reply)

February 8, 2016, 10:10 am

≫ Next: ODBC call failed for linked table, but OK for import? (no replies)

≪ Previous: MySQL trigger to insert to MS SQL Server 2008 ?? (no replies)

$

0

0

Hi,

I have an unusual task. Browser recieves some data by HTML every minute. I don't have any access to the server apart HTML interface. I need to store the data at local DB at client side. I created JS plugin to parse the HTML but I have a question how I can connect to MYSQL DB. I can host the mySQL DBMS at the same host or through network at a remote DB server (not the server which gives data to me). My obstacles are:
1. What should I install?
2. What options to connect I have? I guess one option is ODBC. Probably ADO is another option.
3. Could you please provide simple JS code to connect to mySQL server and execute any simple SQL query.

ODBC call failed for linked table, but OK for import? (no replies)

February 8, 2016, 6:52 pm

≫ Next: The timeout period elapsed prior to obtaining a connection from the pool (no replies)

≪ Previous: MySQL and Javascript at client (1 reply)

$

0

0

I have a new installation of MySQL (5.7) on Windows 10 and trying to use MS Access 2007 as the front-end (which I have done with earlier versions of MySQL & the ODBC driver). I have MySQL ODBC 5.3 32 bit ANSI driver installed.

When I try to *LINK* to the MySQL table from Access, I get ODBC - Call Failed (but it subsequently shows all the table field names, but no data values).

When I try to *IMPORT* the MySQL table data, all is well.

Anyone have any ideas ?

Ian

The timeout period elapsed prior to obtaining a connection from the pool (no replies)

February 9, 2016, 1:44 am

≫ Next: I need an odbc driver to enable Crystal Reports 2013 to connect to MySQL 5.6 (1 reply)

≪ Previous: ODBC call failed for linked table, but OK for import? (no replies)

$

0

0

Hy together,

In my application recently I got this errormessage
"The timeout period elapsed prior to obtaining a connection from the pool"

The application runs about 20days. Then this message occurs.

Does anybody know wherre this message comes from?

my source code:
OPEN connection:



mydbConnection = New MySqlConnection()
mydbConnection.ConnectionString = "server=" & ServerAddress & "user id=" & UserName & "password=" & UserPassword & "database=" & Database & "Allow User Variables=True"
'mydbConnection.ConnectionTimeout = 1
mydbConnection.Open()
mydbCommand = New MySqlCommand()
mydbCommand.Connection = mydbConnection



mySQL Request:
ConnectionPing = mydbConnection.Ping
'wenn keine verbindung besteht, dann öffne sie
If mydbConnection.State <> System.Data.ConnectionState.Open Or ConnectionPing = False Then
mydbConnection.Open()

I need an odbc driver to enable Crystal Reports 2013 to connect to MySQL 5.6 (1 reply)

February 16, 2016, 7:06 am

≫ Next: Specifeid DNS contains an architecture missmatch between the Driver and Application (no replies)

≪ Previous: The timeout period elapsed prior to obtaining a connection from the pool (no replies)

$

0

0

I'm looking for a MySQL ODBC connector driver to enable Crystal Reports 2013 to connect to databases in MySQL 5.6. I've already tried MySQL ODBC connectors, version 5.3.4 and 5.1. I installed the drivers and created DSNs in Windows 7. The problem is that when I went to develop a report in Crystal Reports, I was unable to use the DSNs with the database expert. In all cases, when I tried to connect to the MySQL databases using the DSN, I received an error message in Crystal Reports that said:

"Login Failed. The specified DSN contains an architecture mismatch between the driver and application."

Can anyone recommend a compatible version of the MySQL ODBC driver for Crystal Reports 2013 or, if not, tell some other way to access MySQL databases with Crystal Reports?

Specifeid DNS contains an architecture missmatch between the Driver and Application (no replies)

February 18, 2016, 4:09 am

≫ Next: ODBC support for utf8mb4 (no replies)

≪ Previous: I need an odbc driver to enable Crystal Reports 2013 to connect to MySQL 5.6 (1 reply)

$

0

0

I have installed MySQL 5.5.1-m2-win32 bit version, mysql-connector-odbc-5.1.11-winx64 on Win7 64bit machine.

When I try to make a new connection with Crystal Report 2008, it gives me an error 'Specified DNS contains an architecture missmatch between the Driver and Application'.

Kindly Help With This

ODBC support for utf8mb4 (no replies)

February 19, 2016, 5:31 am

≫ Next: Simply accounting 2010 and Mysql ODBC 3.51 (3 replies)

≪ Previous: Specifeid DNS contains an architecture missmatch between the Driver and Application (no replies)

$

0

0

My C++ application (build in VS2008 with v6.0A Windows SDK) connects to MySQL database v5.5.34 through v5.3 unicode mysql odbc connector.

I changed my table to support utf8mb4 charset.
ALTER TABLE mytable CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

doing that, i can directly enter the supplementary characters to the database.

When, inserting supplementary characters through my c++ app via odbc connector, my odbc driver crashes.


Things which i am using:
IDE: VS2008 with v6.0A Windows SDK
MySQL: v5.5.34
MySQL ODBC: v5.3

Any pointers would be great.

Simply accounting 2010 and Mysql ODBC 3.51 (3 replies)

February 21, 2016, 2:49 pm

≫ Next: Linked Server from SQL to MySQL using an ODBC (no replies)

≪ Previous: ODBC support for utf8mb4 (no replies)

$

0

0

Hi,

I have simply accounting installed on Windows 7-64 and the ODBC Data Source Admin shows Mysql driver 3.51.
When i click configure I get Error The Setup routines for the MySql ODBC 3.51 driver ODBC driver could not be found. Please reinstall driver. Second window opens: The specified driver contains an architecture mismatch between driver and application.

I cannot connect to my DB from Excel Microsoft Query either.

Any help would be appreciated,

Thank you,

Isabel

---

Linked Server from SQL to MySQL using an ODBC (no replies)

February 25, 2016, 6:22 am

≫ Next: mySQL ODBC not registered (1 reply)

≪ Previous: Simply accounting 2010 and Mysql ODBC 3.51 (3 replies)

$

0

0

Hi all,

I was just wondering...
Is it supposed to be slower to connect to a MySQL DB from SQL Linked Server using the MyQSL ODBC than using the ODBC connection directly from some VB.NET CODE.

I wonder if I should run some SQL scripts using a linked server or
write some VB code to connect to the ODBC directly.

Linked server looks like one more step to me but I wonder if it is that much slower.

Thanks!

mySQL ODBC not registered (1 reply)

February 25, 2016, 2:26 pm

≫ Next: Installation of ODBC connector 5.3.6 fails (no replies)

≪ Previous: Linked Server from SQL to MySQL using an ODBC (no replies)

$

0

0

I need to install a 32 bits version of mySQL ODBC connector on a Windows 2008 Server R2. I have installed 32 bits ODBC 5.1 driver without errors but I think it's not correctly installed/registered.

In the 32 bits ODBC Manager (C:\Windows\SysWOW64\odbcad32.exe), drivers, I can see the MySQL ODBC 5.1 Driver but there is nothing in the Version, Organization, File and Date columns.

If I try to create a DSN I get the following error "The setup routines for the MySQL ODBC 5.1 Driver could not be loaded".

Can anybody help me? Thanks in advance.

Installation of ODBC connector 5.3.6 fails (no replies)

March 18, 2016, 12:32 pm

≫ Next: Installation of Connector/ODBC failed on Win10 64-bit (no replies)

≪ Previous: mySQL ODBC not registered (1 reply)

$

0

0

The installation of the current MySQL ODBC connector (mysql-connector-odbc-5.3.6-osx10.11-x86-64bit) on OS X 10.11.3 fails.

The installer creates the folder in /usr/bin and copies all files into this folder. But registration of the driver fails. I was also not able to register the files as described in the manual.

Any ideas? Thanks in advance for any advice!

Installation of Connector/ODBC failed on Win10 64-bit (no replies)

April 1, 2016, 7:28 pm

≫ Next: Failure on installation ODBC-Driver (no replies)

≪ Previous: Installation of ODBC connector 5.3.6 fails (no replies)

$

0

0

Hello,

as well using the windows installer for the entire product as when running mysql-connector-odbc-5.3.6-winx64.msi I receive the error:

"The setup routines for the MySQL ODBC 5.3 ANSI Driver ODBC driver could not be loaded due to system error code 126: The specified module could not be found. (C:\Program Files\MySQL\Connector.ODBC 5.3\myodbc5S.dll).. Verify that the file MySQL ODBC 5.3 ANSI Driver exists and that you can access it."

Indeed, there is no \Connector.ODBC directory in C:\Program Files\MySQL\ after MySql Installer for Windows 5.7 has finished.

What to do next?

Failure on installation ODBC-Driver (no replies)

April 4, 2016, 11:51 pm

≫ Next: odbc install on Windows 2008R2 64bit (4 replies)

≪ Previous: Installation of Connector/ODBC failed on Win10 64-bit (no replies)

$

0

0

I downloaded driver 5.2 (32 bit) Everything woked fine. A connection was there since years.

I have Windows 10 Home und MSO 32 bit.

Now i wanted to install driver 5.3 (32 bit), unsinstalled driver 5.2, installed 5.3. No work! Because driver 5.2 worked, I installed this driver again. No work anymore !! In odbcad32.exe is 5.2 visible, but Version, Firma etc empty !! When you decide to use driver 5.2, a pop appears with "Die Setup-Routinen für den MySQL 5.2 Treiber konnten nicht gefunden werden. Installieren Sie den Treiber neu." after this the popup "Fehler bei ConfigDSN, ConfigDriver oder ConfigTranslator: Fehler gefunden: Komponente wurde in der Registrierung nicht gefunden."

msi with "repair" started. No changes. With "Remove" deleted, after that reinstalled, several boots. I don't know anything more...

Same problem with driver 3.51.30 !

HELP!

odbc install on Windows 2008R2 64bit (4 replies)

April 6, 2016, 8:46 am

≫ Next: Error trying to install ODBC 5.3 on Windows server 2008 (1 reply)

≪ Previous: Failure on installation ODBC-Driver (no replies)

$

0

0

Anybody have any luck with getting MySQL odbc driver installed on Windows Server 2008R2 64bit.

I get the following error during install
"Error 1918.Error installing ODBC driver MySQL ODBC 5.3 ANSI Driver, ODBC error 13: The setup routines for the MySQL ODBC 5.3 ANSI Driver ODBC driver could not be loaded due to system error code 126: The specified module could not be found. (C:\Program Files\MySQL\Connector ODBC 5.3\myodbc5S.dll).. Verify that the file MySQL ODBC 5.3 ANSI Driver exists and that you can access it."

I get the same error with 32bit install.

Error trying to install ODBC 5.3 on Windows server 2008 (1 reply)

April 6, 2016, 8:44 am

≫ Next: Installation fails with El Capitan (no replies)

≪ Previous: odbc install on Windows 2008R2 64bit (4 replies)

$

0

0

I've been getting an error 1918. Error Installing ODBC driver MySQL ODBC 5.3...
Some users have indicated that installing Microsoft Visual Studio C++ redistributable 2010 would solve the issue.

See http://forums.mysql.com/read.php?37,599399,599399

This does not solve the issue. I presently have both VS C++ 2010 x86 and x64 versions installed.

Any other thoughts?

---

Installation fails with El Capitan (no replies)

April 8, 2016, 5:07 am

≫ Next: UNICODE version of the driver (no replies)

≪ Previous: Error trying to install ODBC 5.3 on Windows server 2008 (1 reply)

$

0

0

Hi,
I am desperatly trying to install odbc connector on my mac os 10.11. However when I try installing throught the dmg, the installation fails.
If I try to install it manually, I get some warning :
Library not loaded: /Volumes/hd2/pb2/build/sb_0-18231254-1457619324.6/unixODBC-2.3.2-osx10.11-x86-64bit/lib/libodbc.2.dylib
Referenced from: /usr/local/bin/myodbc-installer
Reason: image not found
Trace/BPT trap: 5
I admit that I can understand something is missing obviously but what to do from there is a mystery.
I have visited dozens of forums/websites and stuff but still out of clues to solve this and I really need to get it working soon for a project.
The installation error dialog invites me to get in touch with the editor but I can't find any dedicated page.
Thanks in advance for your help,
Loic

UNICODE version of the driver (no replies)

April 19, 2016, 9:34 am

≫ Next: How dumb is MySQL, needed 32 bit connector for windows 64 bit (1 reply)

≪ Previous: Installation fails with El Capitan (no replies)

$

0

0

Hi, ALL,
I'm trying to download the MySQL ODBC driver for Windows and install it on Windows 8.1.
However the download page only has an ANSI driver and I'm looking for the Unicode one.

Please advise.

Thank you.

How dumb is MySQL, needed 32 bit connector for windows 64 bit (1 reply)

April 20, 2016, 7:33 am

≫ Next: Connector/ODBC not closing connection properly (Classic ASP/VBS) (no replies)

≪ Previous: UNICODE version of the driver (no replies)

$

0

0

I have a 32 bit development tool, windows 7 runs 32 bit OBDC, And you cannot install MySQL 32 bit OBDC connector on windows 7.
why not!!!!! as its the cure to all 32 bit problems

How stupid is that
may be we should go to mssql thaT IS MORE ORGANISED

Connector/ODBC not closing connection properly (Classic ASP/VBS) (no replies)

April 22, 2016, 5:28 am

≫ Next: ODBC 5.1 driver returns wrong datatype to ADODB (no replies)

≪ Previous: How dumb is MySQL, needed 32 bit connector for windows 64 bit (1 reply)

$

0

0

I have a Classic ASP web applicaton, connecting to my mySQL using ODBC (5.3).
For some reason, the process is not killed when the connection is closed. In the processlist ("SHOW PROCESSLIST"), the connection is present with the command "Sleep". It is killed first when the number of seconds that corresponds to the wait_timeout value in the my.ini file is reached.

How come the connection is still there (risking to use up the max_connections and max_user_connections limits) after the connection is closed?

Simplified code snippet (VBScript):

<%

sConnection = "DRIVER={MySQL ODBC 5.3 ANSI Driver}; SERVER=localhost; DATABASE=db; UID=user;PWD=xxxxxx;"
Set anslutmySQL = Server.CreateObject("ADODB.Connection")
anslutmySQL.Open(sConnection)

SQL = "SELECT ID FROM table LIMIT 1"
SET RS = anslutmySQL.execute(SQL)
ID = RS("ID")

RS.Close : SET RS = Nohting ' Close recordset
anslutmySQL.Close : SET anslutmySQL = Nothing ' Close connection

%>

Language: Classic ASP
OS: Windows Server 2012 R2 / IIS 8.5 64bit
MySQL: 5.5.45 - MySQL Community Server (GPL)
Connector/ODBC version 5.3 ANSI

Thanks.

ODBC 5.1 driver returns wrong datatype to ADODB (no replies)

May 4, 2016, 2:24 pm

≫ Next: ODBC error with Access (no replies)

≪ Previous: Connector/ODBC not closing connection properly (Classic ASP/VBS) (no replies)

$

0

0

0
down vote
favorite


Situation: working with legacy classic ASP code, attempting to move the codebase from an old server to a new one.

The code attempts to connect to a MySQL database on a Windows server using the MySQL ODBC 5.1 driver and the ADODB.Connection object.

Connection String = "Driver={MySQL ODBC 5.1 Driver};Server=dbserver;Database=dbname;Uid=username;Password=password;Option=3"

Query results are returned in ADODB.RecordSet objects. When I try to access a field containing a standard MySQL Integer, I get this error:

Microsoft VBScript runtime error '800a01ca'
Variable uses an Automation type not supported in VBScript

If I manually convert the field using cLng() then the error is eliminated and the correct value is returned. However, there is too much code to manually look for each reference to an integer and manually convert it.

VarType() returns 19 for these values, which appears to be some type of Long datatype that VB doesn't understand. (See here) Isn't the ODBC driver supposed to return VarType 3 for long integers? (see here)

I tried passing the option 16384 (NO_BIGINT) in the "option=" parameter of the connection string but it didn't make any difference.

Any idea how to correct this? It seems there should be an option to pass to the MySQL ODBC driver to return longs as Long Integer datatype, but I can't find it.

Thanks in advance!