After suffereing through this on my Sunday afternoon :)
It appears that the ADO vs ODBC is purely an interface issue...
I have a MDB created explicitly with ADO calls.. that can be read in and
written to by the QODBC interface using the MS Access database type.
Then I can re-use the DB back in the ADO system I have.
> -----Original Message-----
> From: André Somers [mailto:[email protected]]
> Sent: Sunday, June 29, 2008 12:07 PM
> To: [email protected]
> Subject: Re: MS ADO/Jet SQL driver?
> "David Fuess" <[email protected]> schreef in bericht
> news:[email protected]
> > ODBC is not ADO and will not "pick up msado15.dll" they are two
> > and distinct interfaces created by MS. ODBC, the older specification,
> > requires OS interaction via the "ODBC Data Source Administrator" to
> > provide the linkage between the database engine and the program. It
> > requires an engine side ODBC driver, in this case the "Microsoft
> > Driver" to link between ODBC and the database (.mdb file) and an ODBC
> > interface library in your application.
> I'm not sure if you mean that you need to set up an ODBC data
> through the OS in advance, but that certainly is NOT the case. All you
> to do is pass the correct connection parameters as your ODBC database
> No manual setup is required.
> To unsubscribe - send a mail to [email protected] with
> "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
To unsubscribe - send a mail to [email protected] with
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/