MySql OleDb Driver

  • Thread starter Thread starter Rick Strahl [MVP]
  • Start date Start date
R

Rick Strahl [MVP]

Has anybody worked with teh MySql OleDb provider before?

I got MySql up and running and tested with the native .Net drivers (which
works Ok), but wanted to see if the OleDb driver would work as well...
Couldn't get that to work though...

It seems that the OleDb driver is failing on every query returning an
incredibly helpful:

No error information available: DB_E_NOTABLE(0x80040E37).

This on a SELECT * from wws_customers where there couldn't be anything
wrong. Connection seems to be Ok. This is all happening in the business
tier, but the same OleDb code is used with other providers without any
problems.

Anybody seen this behavior before?

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/webblog/
 
Right. The ByteFx drivers work fine.

The main reason is that this is a generic tool and I need to make sure that
things work with various providers. The main reason is that the ByteFx
drivers require a separate installation that must be user provided (due to
the GNU licensing) so it would be nice if I could get things to work out of
the box without installing anything.

At this point I'm also curious why the OleDb driver is outright failing.

Tried the Odbc driver and that works to some degree, but there are all sorts
of data type conversion problems.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/webblog/
 
Rick Strahl said:
Right. The ByteFx drivers work fine.

The main reason is that this is a generic tool and I need to make sure that
things work with various providers. The main reason is that the ByteFx
drivers require a separate installation that must be user provided (due to
the GNU licensing) so it would be nice if I could get things to work out of
the box without installing anything.

Ah, I see.
At this point I'm also curious why the OleDb driver is outright failing.

I guess the provider didn't implemented or it has a fault implementation of
certain method(s).
Tried the Odbc driver and that works to some degree, but there are all sorts
of data type conversion problems.

Yes, the provider implementation..
 
Back
Top