Answered by:
My Sql Connection

Question
-
User-151352204 posted
Hi My connection to my sql is
string ConnectionString = @"Provider={MySQL ODBC 3.51 Driver};SERVER=XXX;PORT=3306;DATABASE=ARP;USER=XXX;PASSWORD=XXX;OPTION=17923";
shows error ;
The '{MySQL ODBC 3.51 Driver}' provider is not registered on the local machine.
How to solve it. I install OBDC 3.51 connector.
Monday, July 21, 2014 4:12 PM
Answers
-
User281315223 posted
You should be able to download and install the appropriate ASP.NET MySQL ODBC drivers from this site.
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Monday, July 21, 2014 4:47 PM -
User281315223 posted
Have you tried making the change that the message suggests and adding the System.Data.Odbc assembly as a reference?
You would just need to right-click the References section of your application and scroll until you find System.Data.Odbc and then add it. You'll likely need to include the appropriate using or Imports statements in areas that you are building your ODBC Connections as well.
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Tuesday, July 22, 2014 12:30 AM
All replies
-
User281315223 posted
You should be able to download and install the appropriate ASP.NET MySQL ODBC drivers from this site.
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Monday, July 21, 2014 4:47 PM -
User-151352204 posted
Still it shows same error after I install MY SQL OBDC 3.51 driver. Can you tell me why? Iam using VS2005.
Thanks
Monday, July 21, 2014 5:21 PM -
User-151352204 posted
Error :
The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).
Monday, July 21, 2014 6:10 PM -
User281315223 posted
Have you tried making the change that the message suggests and adding the System.Data.Odbc assembly as a reference?
You would just need to right-click the References section of your application and scroll until you find System.Data.Odbc and then add it. You'll likely need to include the appropriate using or Imports statements in areas that you are building your ODBC Connections as well.
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Tuesday, July 22, 2014 12:30 AM