Is there a registration issue? When I've seen ODBC work in the

Administrator but not in the app it turned the driver was not fully

registered.

-dta

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On

Behalf Of Ted Roche

Sent: Saturday, January 08, 2005 12:15 PM

To: profoxtech@leafe.com ProLinux Email List

Subject: VFP to MySQL 4.1.8 via MyODBC: "Could not determine the driver

name"

Just installed a new LAMP box with MySQL 4.1.8 and also upgraded my

Windows XP client to the latest MyODBC 3.51.10.00 and I'm having

trouble connecting the two. Setting up a DSN in the ODBC administrator

passes the "Test" button test. Attempting to connect from another

application - xCase or VFP - throws an error "[MySQL][ODBC 3.51 Driver]

Could not determine the driver name so could not lookup setup library"

and error HY000, the general error. Has anyone seen this and know of a

fix?

A Google didn't produce any clues. There's a similar post from someone

using Access posted last week:

http://forums.mysql.com/read.php?37,10223,10223. No replies, though.

Cross-posting to ProFox and ProLinux as I'm not sure if this is a

client or server issue.

Telnet is displaying the server responding on the IP address, so it's

not a firewall issue.

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com

[excessive quoting removed by server]

On Jan 8, 2005, at 5:19 PM, David T. Anderson wrote:

> Is there a registration issue? When I've seen ODBC work in the

> Administrator but not in the app it turned the driver was not fully

> registered.

Great idea, dta. Looked in the Registry and all looked well. Rebooted

the machine and it started working better. Got a new error, "Access

Denied," which is just an authentication issue. Gotta review my GRANT

commands to see if I missed something. Also, the MySQL 4.1.x uses a new

password encryption technique on the server, which I've heard can cause

some problems with older drivers, particularly with PHP. Will continue

to plug at it.

Thanks for the suggestion.

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com

Update: spent a day or two trying every variation of SQLStringConnect()

from VFP. The bad ones gave me "Access Denied." The really bad ones

crashed VFP. How rude!

I was able to connect to the database using a *User* DSN from xCase and

manipulate data. Haven't figured out how to get it to work from VFP.

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com

Ted,

Have you thought about dropping back one or two minor versions to an

earlier ODBC driver?

Is there a MySQL forum where you can post your findings? I wonder if the

new version of the MySQL ODBC driver was adequately tested?

Is there a way to run ODBC in a DEBUG mode that might provide additional

clues?

Malcolm

----- Original message -----

From: "Ted Roche" <tedroche@tedroche.com>

To: profoxtech@leafe.com

Date: Mon, 10 Jan 2005 15:58:17 -0500

Subject: Re: VFP to MySQL 4.1.8 via MyODBC: "Could not determine the

driver name"

Update: spent a day or two trying every variation of SQLStringConnect()

from VFP. The bad ones gave me "Access Denied." The really bad ones

crashed VFP. How rude!

I was able to connect to the database using a *User* DSN from xCase and

manipulate data. Haven't figured out how to get it to work from VFP.

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com

[excessive quoting removed by server]

On Jan 10, 2005, at 4:08 PM, Malcolm Greene wrote:

> Have you thought about dropping back one or two minor versions to an

> earlier ODBC driver?

If I must. I'll lose some security patches that way.

> Is there a MySQL forum where you can post your findings? I wonder if

> the

> new version of the MySQL ODBC driver was adequately tested?

Yup. Done that. Participating in several promising threads.

> Is there a way to run ODBC in a DEBUG mode that might provide

> additional

> clues?

Yes, like most ODBC drivers, you can record the low-level exchanges.

I've done this, and offered to post a few to the MySQL boards, as

there's not much in there that means much to me.

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com

On Jan 10, 2005, at 4:08 PM, Malcolm Greene wrote:

> Have you thought about dropping back one or two minor versions to an

> earlier ODBC driver?

It's worth a try. I was hoping for confirmation that someone else might

have run into the problem, to eliminate the possibility that it was

something unique to my setup.

> Is there a MySQL forum where you can post your findings? I wonder if

> the

> new version of the MySQL ODBC driver was adequately tested?

Yup, been following a thread and adding my "Me, too!" to the

complaints. A MySQL employee just confirmed the problem, promised a fix

soon and suggested... dropping back a minor version. Great minds think

alike, I guess!

Trying that now...

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com

Ted,

I'm using an older version of the MySQL ODBC driver in a limited

capacity against a MySQL database hosted on a 3rd party hosting site

(LunarPages). Within my limited scope (limited by my needs vs. limited

by MySQL capabilities) everything works great. BTW: My success in this

area due to the contributions of many on this forum including Ed Leafe,

Paul McNett, Bill Sanders and yourself.

Thanks for keeping us in the loop with your MySQL ODBC driver woes. If

there's something I can test for you in my environment feel free to

contact me off list and I'll give it a shot.

Malcolm

<snip>

From: "Ted Roche" <tedroche@tedroche.com>

To: profoxtech@leafe.com

Date: Tue, 11 Jan 2005 09:22:03 -0500

Subject: Re: VFP to MySQL 4.1.8 via MyODBC: "Could not determine the

driver name"

Yup, been following a thread and adding my "Me, too!" to the

complaints. A MySQL employee just confirmed the problem, promised a fix

soon and suggested... dropping back a minor version. Great minds think

alike, I guess!

</snip>

Malcolm:

Thanks for the thoughts and support.

I was able to confirm that the problem was the ODBC driver, and not

something with the configuration on either the windows box nor the

server. FYI for anyone playing with a MyODBC solution this week: use

the previous driver, 3.51.09.00 and not the most recent, 3.51.10.00.

Ted Roche

Ted Roche & Associates, LLC

http://www.tedroche.com