Re: Connection MySQL through ADO with MyOLEDB provider

> try {
> command->CommandText = query.data();
> recordset->Open ( (IDispatch *) command, vtMissing, adOpenStatic,
> adLockBatchOptimistic, adCmdUnknown);
> }

You need to have a connection for command object. Do you have one?
Other than this it looks fine. It is probably a MYOLEDB problem

You don't report the version number of MYOLEDB

What I would do is this:

1. See if you can find a later provider (driver) of MYOLEDB that fixes this
problem
2. Failing that, find out if this is a known problem with this provider and
if there are any workarounds.

S


.

Relevant Pages

  • Re: ADO und MySQL
    ... >>> OLE DB provider for ODBC. ... >> Kannst Du MyOLEDB verwenden? ...
    (microsoft.public.de.access.clientserver)
  • Re: ADO und MySQL
    ... handelt es sich bei diesen Providern um Treiber ... Dateien die am Client installiert werden wollen. ... "MyOLEDB is not officially supported by MySQL." ... >> ein MS OLE DB Provider genutzt wird. ...
    (microsoft.public.de.access.clientserver)
  • Re: Connection MySQL through ADO with MyOLEDB provider
    ... Well it's MyOLEDB v3.0 and as long as I know it's the latest version. ... Of course I have a connection object!! ... find out if this is a known problem with this provider ... Prev by Date: ...
    (microsoft.public.data.ado)
  • Re: return OleDbDataReader from static function
    ... If you were to use some provider specific API's, like the one for oracle, ... statements everywhere, and you need just one variable for the connection, ... > dim cnOleDb as new OleDbConnection ... > <use cnOleDb in my command object> ...
    (microsoft.public.dotnet.framework.adonet)