VBA Myltiple queries (1 reply)

July 2, 2013, 4:39 am

≫ Next: Correct connectionstring for ODBC 5.2.5 (2 replies)

≪ Previous: Data source cannot be found (ODBC 5.2.5) (3 replies)

$

0

0

I am working in VBA through Excel 2010. I have one piece that works marvelously, and using the same method for another query, I get an automation error on the line where I put

records.Open query, conn

Where query2b is my query and c_n is my connection that I used in an earlier successful query.
my successful query looks like this:

query1 = "SELECT ..."
r_s.Open query1, Conn, adOpenStatic 'r_s is the ADODB recordset
...
r_s.Close

but then when I do the next query,
I have query2 = "SELECT ..."
Set records = CreateObject("ADODB.Recordset")
records.Open query, Conn, adOpenStatic


And VBA just gives me
"Run-time error '-2147217887 (80040e21)':
Automation error

Help Please?

---

Correct connectionstring for ODBC 5.2.5 (2 replies)

July 3, 2013, 2:59 am

≫ Next: ODBC 5.2.5 ConnectionString for 64bits systems (2 replies)

≪ Previous: VBA Myltiple queries (1 reply)

$

0

0

Hello,

I'm using ODBC connectors for a very long time.

- For ODBC 3.51 I'm using the following connection string:

("Driver={MySQL ODBC 3.51 Driver};Server=localhost;Port=3306;Database=mydatabase;User=root;Password=mypass;Option=3;")


- For ODBC 5.1 I'm using the following connection string:

("Driver={MySQL ODBC 5.1 Driver};Server=localhost;Port=3306;Database=mydatabase;User=root;Password=mypass;Option=3;")


- For ODBC 5.2.4 I'm using the following connection string:

("Driver={MySQL ODBC 5.2a Driver};Server=localhost;Port=3306;Database=mydatabase;User=root;Password=mypass;Option=3;")


- But for the latest version 5.2.5, When I use the following connection:

("Driver={MySQL ODBC 5.2a Driver};Server=localhost;Port=3306;Database=mydatabase;User=root;Password=mypass;Option=3;")

An exception is throw saying that: ERROR [IM002] data source not found and driver name not specified


So please can you tell me the correct connectionstring to use with this latest version (5.2.5). I'm using the 32bits version of this driver

Thanks

ODBC 5.2.5 ConnectionString for 64bits systems (2 replies)

July 8, 2013, 8:03 am

≫ Next: Password for MySQL DB (1 reply)

≪ Previous: Correct connectionstring for ODBC 5.2.5 (2 replies)

$

0

0

Hello,

I'm able to connect with the latest ODBC driver 5.2.5 on 32bits systems with this connectionstring:

("Driver={MySQL ODBC 5.2 ANSI Driver};Server=localhost;Port=3306;Database=mydatabase;User=root;Password=mypass;Option=3;")

but on 64bits systems an exception occurs saying: ERROR [IM002] data source not found and driver name not specified.

Can you please show me the correct ODBC 5.2.5 connectionstring for 64bits systems ?

Regards

Password for MySQL DB (1 reply)

July 9, 2013, 12:38 am

≫ Next: ADODB, 32 bit MySQL ODBC 5.2 Unicode: Tables with multiple blob fields fail (no replies)

≪ Previous: ODBC 5.2.5 ConnectionString for 64bits systems (2 replies)

$

0

0

Please forgive me for a really stupid question, but it's been years since I've used MySQL, and I've forgotten a lot...

In the connection string, a username and password are required - Is this a username/password that I would have defined at the time I created the database, or is it one defined by my host?

ADODB, 32 bit MySQL ODBC 5.2 Unicode: Tables with multiple blob fields fail (no replies)

July 7, 2013, 1:54 pm

≫ Next: MySQL ODBC 5.02.05.00 Driver for Windows x86 64-bit (2 replies)

≪ Previous: Password for MySQL DB (1 reply)

$

0

0

Hi,
I have found a problem with 32bit ODBC Unicode Driver:

When I try to insert a record in a table with more than one BLOB field, I will get a buggy result, but no Errors are thrown.

The table has the following structure:

delimiter $$

CREATE TABLE `sce_usernames` (
`SUsername` varchar(50) NOT NULL DEFAULT '',
`SUserPassword` blob,
`SUserRights` blob,
PRIMARY KEY (`SUsername`),
UNIQUE KEY `SUsername_UNIQUE` (`SUsername`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8$$

When I try to insert a record with ADODB

SUserName = 'Admin' and filled BLOB data, I will get the result

Empty SUserName, SUserPassword NULL, SUserRights BLOB

The same Statement works with MS SQL Server 2008, Access.

I suppose the ODBC Driver has a bug handling tables with more than one blob, because tables with only one blob field are handled correctly.

Thanks for helping me with this issue

René

MySQL ODBC 5.02.05.00 Driver for Windows x86 64-bit (2 replies)

July 10, 2013, 11:16 pm

≫ Next: Connection Failedon ODBC - After Moving Server to new Subnet and Changing IP (no replies)

≪ Previous: ADODB, 32 bit MySQL ODBC 5.2 Unicode: Tables with multiple blob fields fail (no replies)

$

0

0

Updated to MySQL ODBC 5.02.05.00 Driver for Windows x86 64-bit on a development server. I created a UNICODE DSN (which is the 5.2w driver?) and connections to MySQL databases generate this error:

Connection Failed [HY000][MySQL][ODBC 5.2(w) Driver] Connection using old (pre-4,1,1) authentification protocol refusted (client option 'secure_auth' enabled).

I have added C:\my.cnf and enabled "Read options from my.cnf" on the MISC tab and I still get the 'secure_auth' error.

[client]
secure-auth=off


On the production server, the drivers are 5.02.02.00 (5.2w) and same DSN connections work (no my.cnf file; option disabled).

Connection Failedon ODBC - After Moving Server to new Subnet and Changing IP (no replies)

July 9, 2013, 3:15 am

≫ Next: Unable to Duplicate Error Binary Logging Not Possible... (2 replies)

≪ Previous: MySQL ODBC 5.02.05.00 Driver for Windows x86 64-bit (2 replies)

$

0

0

Hello

I have just inherited a CentOS 6.3 box (Linux 2.6.32-279.el6.x86_64 on x86_64) running MySQL 5.1.61.

This was a virtual server running on Windows Hyper-V which I have now migrated over to my VMware estate and changed the IP address on to put it on our subnet.

I can connect to the box just fine, and perform an array of tasks. However I cannot setup an ODBC connection.

The staff who use the database on there reported that their ODBC connections no longer worked (even after they updated the IP address in the connector).

I have installed the MySQL ODBC driver (5.01.12.00) onto my desktop machine (Windows 7 Pro 64-Bit - as are the other workstations trying to use the connector).

When then trying to setup the connector, I point it to the IP of the server (port 3306 - which was the port used before I inherited it and not something I have changed). Using either the username they used previously (dbuser) or root, I am unable to connect. Get the following error every time:

Connection Failed: [HY000][MySQL][ ODBC 5.1 Driver]Access denied for user 'root'@'mycomputername' (using password: YES).

Can anyone offer any suggestions or advice?

I am not a CentOS expert (or MySQL for that matter) - my skills lie in Windows. But I can do basic tasks and thought that simply changing the IP of the server and pointing the users to it would do the trick!

Thanks in advance.

Unable to Duplicate Error Binary Logging Not Possible... (2 replies)

July 9, 2013, 4:02 pm

≫ Next: Unable to uninstall MySQL ODBC Connector on RHEL 5.4 (1 reply)

≪ Previous: Connection Failedon ODBC - After Moving Server to new Subnet and Changing IP (no replies)

$

0

0

Hi Guys,

I created a connection to a MySQL database from Oracle using Oracle Gateway for ODBC. I am able to read however when attempting to insert I receive the error "[MySQL][ODBC 5.2(w) Driver][mysqld-5.1.61-0ubuntu0.10.04.1-log]Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT". Now I am trying to replicate this error on a local installation of MySQL however I'm unable to. The config settings seems very similar. Any ideas?

---

Unable to uninstall MySQL ODBC Connector on RHEL 5.4 (1 reply)

July 17, 2013, 8:36 am

≫ Next: My SQL ODBC driver (no replies)

≪ Previous: Unable to Duplicate Error Binary Logging Not Possible... (2 replies)

$

0

0

We have an existing mysql-odbc connector installed on Linux-RHEL machine.
Here is the proof of installation.
[root@Config5364Lvm0 Mysql_ODBC_Connectors]# rpm -qa | grep mysql
mysql-connector-odbc-5.2.5-1.rhel5

But we have some connectivity issue with currently installed MySQL ODBC connector. So we wanted to un-install and re-install this connector.

When I try to un-install, I get below error.
[root@Config5364Lvm0 Mysql_ODBC_Connectors]# rpm -e mysql-connector-odbc-5.2.5-1.rhel5
[ERROR] SQLInstaller error 6: Unable to find component name
error: %preun(mysql-connector-odbc-5.2.5-1.rhel5.x86_64) scriptlet failed, exit status 1

When I try to replace the installation, get some different error.
[root@Config5364Lvm0 Mysql_ODBC_Connectors]# pwd
/u01/app/dq_admin/Mysql_ODBC_Connectors
[root@Config5364Lvm0 Mysql_ODBC_Connectors]# rpm -iv --replacepkgs mysql-connector-odbc-5.2.5-1.rhel5.x86_64.rpm
Preparing packages for installation...
mysql-connector-odbc-5.2.5-1.rhel5
[ERROR] SQLInstaller error 6: Unable to find component name
error: %post(mysql-connector-odbc-5.2.5-1.rhel5.x86_64) scriptlet failed, exit status 1

And the fresh installation says, rpm already installed.
[root@Config5364Lvm0 Mysql_ODBC_Connectors]# rpm -i mysql-connector-odbc-5.2.5-1.rhel5.x86_64.rpm
package mysql-connector-odbc-5.2.5-1.rhel5.x86_64 is already installed

Tried several ways killing hours and have no idea on how to resolve this. Currently blocked with some testing of our application.
Thus need your kind assistance on getting mysql_odbc connector working. Thanks much.

My SQL ODBC driver (no replies)

July 22, 2013, 10:58 am

≫ Next: How I can link my ODBC data? (no replies)

≪ Previous: Unable to uninstall MySQL ODBC Connector on RHEL 5.4 (1 reply)

$

0

0

Hi,

I am trying to find a 32bit ODBC driver for MySql DMBS version: 5.1.68-rel14.5-log. When I use TeraData SQL assistant to run the queries, I am able to use the driver "MySQL Connector/ ODBC 5.2(w)" to connect to DBMS version "5.5.30-30.2-log" successfully the same driver does not load the list of all the tables for the DBMS version "5.1.68-rel14.5-log" and the system just hangs up. When I use Business Objects to connect to MySQl and the connection works fine but it does not load all the tables in Business Objects too. Please let me know if I should go for any other driver to connect to "5.1.68-rel14.5-log" version.

How I can link my ODBC data? (no replies)

July 23, 2013, 11:56 pm

≫ Next: ODBC Connector for Mac Lion -- installation problem (no replies)

≪ Previous: My SQL ODBC driver (no replies)

$

0

0

Hi!!!

I have my datas are by ODBC because if I try to link it by Access I can do it with this button.



And later I have my database here.



What is the way if you want to do it by MySQL?

Thanks!

ODBC Connector for Mac Lion -- installation problem (no replies)

July 24, 2013, 3:13 am

≫ Next: Queries that run instantly on Workbench take forever on ODBC (no replies)

≪ Previous: How I can link my ODBC data? (no replies)

$

0

0

I'm trying to install the ODBC Connector for Mac OS X 10.7 (Lion). The .dmg installer fails at the last minute with an uninformative error message: "**The installation failed.** The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance." There is also a message bar across the top of the installer window that runs out and does not scroll: "There were errors with the installation. You may want to try i[".

The installer has succeeded in putting libmyodbc5w.so in /usr/local/lib/ and myodbc-installer in /usr/local/bin/. Now, the Read Me file in the .dmg installer says that there should also be a library file libymodbc3S.*, but this has not been installed by the .dmg installer, and it does not exist in the .tar.gz distribution. Is this an error in the documentation, or a missing file?

Furthermore, the instructions in http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation-binary-macosx.html (5.6 Reference Manual :: 22.1.3.3 Installing Connector/ODBC on Mac OS X) are evidently incompletely updated from a previous version. Step 2 reads "Extract the archive: shell> tar xvzf mysql-connector-odbc-5.x.y-osx10.z-x86-(32|64)bit.tar.gz". This is fine: the file I've got is 5.2.5, osx10.7, and 32bit. Step 3 is non-version-specific.

But Step 4 reads "Finally, register the driver with iODBC using the myodbc3i tool you just installed: shell> myodbc3i -a -d -t"MySQL ODBC 3.51 Driver;Driver=/usr/local/lib/libmyodbc3.so;Setup=/usr/local/lib/libmyodbc3S.so"
To verify the installed drivers, either use the ODBC Administrator application or the myodbc3i utility: shell> myodbc3i -q -d". This is out of date -- I'm dealing with the 5.2.5 driver, not 3.51, and the filenames are not what I have.

What do I need to do to register the driver? Is there a missing setup file? How should the command *actually* read?

TIA,
Jeff

Queries that run instantly on Workbench take forever on ODBC (no replies)

July 25, 2013, 5:45 pm

≫ Next: 5.1.12 Max_Column_Name_Len returns 192 (1 reply)

≪ Previous: ODBC Connector for Mac Lion -- installation problem (no replies)

$

0

0

Hello everyone, I have a very old VB6 application that uses the MYSQL ODBC driver to connect to a MYSQL Database. Certain queries are taking forever and the application hangs. I debbugged the aplication and those queries ran OK locally on the server using MYSQL query browser (these queries deliver a single row and run instantly on the query browser). However, the machines that have the VB6 application installed get stuck on those queries. Also, on one of the machines I ran the query using MYSQL Workbench and it ran fine.

The VB6 application worked without a problem until today, nothing was modified recently.

When looking at the queries from either the administrator or workbench, I do not see the query as it is supposed to be running. For example, the query that is run from the application is something like this: "select max(value) from table where conditions" (the table is relatively small) but on the administrator it shows "select * from table" and also it stays at the "writing to net" status.

Any idea of what is going on?

Your help would be very much appreciated.

5.1.12 Max_Column_Name_Len returns 192 (1 reply)

July 31, 2013, 11:15 pm

≫ Next: linked server unable to begin a distributed transaction (no replies)

≪ Previous: Queries that run instantly on Workbench take forever on ODBC (no replies)

$

0

0

While using the ODBC driver version 5.01.04 and SQLGetInfoW was returning a correct length 64 for SQL_MAX_COLUMN_NAME_LEN, but when we transitioned to version 5.1.12 SQL_MAX_COLUMN_NAME_LEN and SQL_MAX_TABLE_NAME_LEN both are returning lengths of 192. Testing it, the limit still seems to be 64 as listed in the all the documentation, but for some reason we are being returned a length of 192. Has anyone else seen this and is there a reason for it? I am just trying to avoid hard-coding a maximum size of 64.

Thanks!

linked server unable to begin a distributed transaction (no replies)

August 8, 2013, 3:08 pm

≫ Next: ODBC Connector Driver Issue Mac OS 10.8.4 (no replies)

≪ Previous: 5.1.12 Max_Column_Name_Len returns 192 (1 reply)

$

0

0

This is a bit complex, but I've been running a Microsoft SQL 2000 server on Windows 2000 Server, linked to a MySQL database for a number of years. Recently I upgrade the M$ box to Windows 2008R2, with SQL Server 2008R2. Now it seems that we get an error when UPDATING some records:

[Microsoft]{ODBC SQL Server Driver][SQL Server] OLD EB provider"MSDASQL" for links server "exmaple" returned message "[MySQL][ODBC 3.51 Driver]Optional feature not supported". [Microsoft]{ODBC SQL Server Driver][SQL Server] The operation could not be performed because OLE DB provider "MSDASQL" for linked server "example" was unable to begin a distributed transaction.

I've tried everything I can think of but to no avail, including simply disabling distributed transactions in the ODBC connection

*Other, non-distributed transactions work fine.
*The MySQL table type is INNODB.
*MSDTC is installed an runinng with inbound and outbound enabled, no auth. required.

---

ODBC Connector Driver Issue Mac OS 10.8.4 (no replies)

August 9, 2013, 4:55 am

≫ Next: ODBC Driver error (no replies)

≪ Previous: linked server unable to begin a distributed transaction (no replies)

$

0

0

I'm on Mac OS X 10.8.4 and the ODBC driver installation fails at the very end.

I went ahead and installed ODBC Administrator from Apple's website and it lists the 5.2.5 driver, so I was able to add a User DSN entry.

But when I try to connect to a database from my Java code in NetBeans, I get this exception: "java.sql.SQLException: No suitable driver found for jdbc:odbc:<my db name>"

Obviously I am also using jdbc. But I downloaded Connector/J and I didn't see any problems with it, though I could be wrong.


Any suggestions?

ODBC Driver error (no replies)

August 12, 2013, 10:43 pm

≫ Next: open up my 4DD database in MYSQL Command Line (no replies)

≪ Previous: ODBC Connector Driver Issue Mac OS 10.8.4 (no replies)

$

0

0

i Get this error every time i try to update a record am totally new here am moving from access to Mysql

here if the code i have

Set Rs = New ADODB.Recordset
Rs.Open "Select stank from sidetank where job_id='" & txtname & "'", FrmMother.Db, adOpenKeyset, adOpenDynamic
Rs(0) = Val(Rs(0)) + Val(Text7)
Rs.Update
Rs.Close

the error happens on the rs.update
please help

open up my 4DD database in MYSQL Command Line (no replies)

August 13, 2013, 7:08 am

≫ Next: MySql Query Help (1 reply)

≪ Previous: ODBC Driver error (no replies)

$

0

0

HEllo all please excuse the (noobness) of my question. But I am a bit confused at the moment. I am trying to connect 4DD database to a program (Its called starship if youre interested) and I was told that I need to connect my 4DD database to a odbc connector in order for the program to "talk to" my database. That is as far as ive gotten. I am not sure where I am supposed to go or what I am supposed to download in order to get my 4DD database to connect with ODBC and ultimately to starship. Any help will be greatly appreciated.

MySql Query Help (1 reply)

August 15, 2013, 1:16 pm

≫ Next: Classic ASP, MySQL or ODBC UTF8 encoding (no replies)

≪ Previous: open up my 4DD database in MYSQL Command Line (no replies)

$

0

0

SELECT CONCAT(LastName, ', ', FirstName) AS "FULL NAME", studentcourse.CourseID AS "COURSE", studentcourse.Status AS "STATUS"
FROM studentcourse, student
where student.studentID=studentcourse.StudentID and Student.IsActiveFlag='1' and Studentcourse.PercentComplete = '66'
order by LastName

I have student, studentcourse and courses tables. One field I am selecting is the percentage of courses students have completed towards a certification. Instead of displaying the percentage stored in the field I have been asked to display a status as below:

Percent Complete = 0; Training Status would be Assigned; Certification Status-N/A
Percent Complete = 33;Training Status would be In-Progress; Certification Status-Pending
Percent Complete = 66;Training Status would be Complete; Certification Status-In-Progress

How display the percentage as the above verbage instead of the percentage?

Sample Data: Percentage column is being removed.
FULL NAME COURSE TRAINING STATUS %Complete CERT STATUS
Adkins, Willa DECC_PER not attempted 0 not attempted
Adkins, Willa LMS_Training_DECC not attempted 0 not attempted
Akers, Dianne DECC_PER not attempted 0 not attempted
Akers, Dianne LMS_Training_DECC not attempted 0 not attempted
Alexander, Richard DECC_PER not attempted 0 not attempted
Alexander, Richard LMS_Training_DECC not attempted 0 not attempted
Altamirando, Ardella 8570_Pending_CE_NE completed 100 completed
Altamirando, Ardella 8570_Pending_IA completed 100 completed

Classic ASP, MySQL or ODBC UTF8 encoding (no replies)

August 16, 2013, 2:10 am

≫ Next: ODBC (no replies)

≪ Previous: MySql Query Help (1 reply)

$

0

0

I have a website hosted with GoDaddy, including MySLQ database on the back end. The site is a Slovenian site, so special characters are used.

The website is built in classic ASP and I have all the pages created in Notepad++ where utf-8 encoding is used. At the top of every page I also have Session.CodePage=65001, Session.LCID=1060 and Response.Charset="utf-8". MySQL db and all the tables are also utf8 encoded.

If I look at the data directly in db through Workbench interface, everything is ok, including some special Slovenian characters I use, like: č

If I go to my website, the Slovenian characters are also printed just fine, including č

The only problem is, that on the same page, data retrived from MySQL is not coded correctly, so letter č becommes ?

What could be the problem and how to solve it?

First I thought it is the MySQL ODBC 3.51 Driver, which I use to connect to db. I have tried adding charset=utf8 to the connection string, but didn't work. I have also tried adding charset=ucs2 to the connection string, which is a tip I found on another website, but it didn't help either. GoDaddy is not supporting MySQL ODBC 5.1 Driver, which could be a solution.

I am running out of options, so please help.