Problem Connecting MySql Through ASP

Problem Connecting MySql Through ASP


I installed the MYSQL ODBC 3.51 and I've used my Mysql database with Visual Basic programming for quite some time now, and it works great.

But now I have to develop a webpage in ASP.

There seems to be a problem with the connection string:

connection.Open "PROVIDER=MSDASQL;driver={MySQL ODBC 3.51 Driver};server=localhost;uid=user;pwd=password;dat
abase=mydb;"

The thing is that this String has worked once or twice and most of the time it doesn't, while the DSN and the database connection in Visual Basic always works.

I have never changed the string, I've used other strings, like the one I read in the whole "Using MyODBC To Access Your MySQL Database Via ASP" article By: Annette Tennison, but still it gives me this error:

Can't find the database source or didn't specify the default driver

I thought that maybe the application "WinMySqladmin Ver 1.4" that comes with the Mysql installation waas the problem, but the problem happens WITH the application running and WITHOUT it.

Many people respond telling me to check the connection string, or maybe create a system dsn and connect directly, but I have done that already 1000 times, and the code is right, I believe there is a configuration problem with my IIS or the Mysql ODBC.


Any ideas???

sorry I tried to find help for it, but im thinking its an account issue rather than code and what not. try setting up an account for the user your trying to log in as in your mysql database, as well as windows account. I had to do this with my Windows 2000 and XP box with IIS 5 running also i was using ASP.Net. For some reason the web page would try to log in as ASPNET. So i had to set up an account using ASPNET as the username..not sure why or if that was really the problem, but it did work after i did it.

Sorry i couldnt say more on this. gl


Actually now that I look at it, it wont be an account error..my bad. It helps if I actually READ your post before i reply

anywho, is that your exact connection string you're using? If so there's a semi-colon on the Database variable that could cause an error. And it does make things alot easier having a DSN for this.things im sure you already know..ok im still looking. if you find a fix let me know.ill add it to my list of 'Things that are 'fixes' List'

There's quite a few threads on or similar to this topic - do a search first - you might find the answer in one of them.