calling MySQL stored procedures from VBScript

[MDCrab]

does anyone have the trick for calling mysql stored procs from VBScript?

I keep getting: "Procedure X can't return a result set in the given context."

I asked at mysql; here's my question put there:

http://forums.mysql.com/read.php?10,228573,228573#msg-228573

thanks,

 

[ingresman]

Yes, I understand that but if the issue is with the version of the ODBC driver, the OLEDB provider may not suffer the same limitation.

 

[MDCrab]

Ingresman,

i appreciate the suggestion. However, when I try to use this connection string:

"Provider=MSDASQL; DRIVER={MySQL ODBC 3.51Driver}; SERVER= localhost; DATABASE=Your_MySQL_Database; UID= Your_Username; PASSWORD=Your_Password; OPTION=3"

--I get errors. If I keep 'MSDASQL', I get: "Data source name not found and no default driver specified."

If I change 'MSDASQL' to the name of my DSN (which I created via my hosting company's control panel), I get: "Provider cannot be found. It may not be properly installed."

so i'm a little unclear what to put in for the provider.

Your help is appreciated. thanks.

 

[MDCrab]

Tsuji,

you wrote: "...Go to control panel and under system info, there is an odbc info. Click it out and look for the MySQL driver build. Specific attention is on the minor build. Even with MySQL 5.0, the driver is an independent downloadable update. You can even blindly download the latest odbc driver for windows from the mysql site and install the latest - that's is important, because, legacy version contains bugs for calling stored procedure."

Now, my hosting company says: "We have updated the driver to the latest version (5.1.5)."

However, every time I run this statement:
response.write "driver version: " & Conn.properties("driver version").value & "<br />"

...it gives me 03.51.04.

Now, i think the hosting company went to this page:

http://dev.mysql.com/downloads/connector/odbc/5.1.html

then i think they downloaded the 5.1.5 download. (They also rebooted the server.)

However, i'm seeing no change with the minor build of the ODBC driver.

Do you see what they did wrong?

thanks,

 

[tsuji]

The driver is an independent updatable download.

http://dev.mysql.com/downloads/connector/odbc/3.51.html

 

[ingresman]

You seem to have used a mixture of the microsoft SQL server provider and ODBC connections in your example

Provider=MSDASQL; DRIVER={MySQL ODBC 3.51Driver}; SERVER= localhost; DATABASE=Your_MySQL_Database; UID= Your_Username; PASSWORD=Your_Password; OPTION=3"

but what you need to do ie

Provider=MySQLProv;Data Source=Your_MySQL_Database;User Id=Your_Username; Password=Your_Password

Notice the differecnt name of the provider. One final point you did use your database name, user name and password not the literal value Your_MySQL_Database etc ?

 

[MDCrab]

Hey Tsuji & Ingresman,

i'm very pleased to report that it now works.

I get back: 05.01.0005 as the driver now.

The connection string needed to change to: DRIVER={MySQL ODBC 5.1 Driver}; ...

thanks so much for the help. I can't say enough about how great this forum is.

thanks,

 

[tsuji]

Good to hear!

 

[ingresman]

it was Tsuji really !