I'll add my two cents along with what everyone else has said because I have
worked with all three.
In short, MySQL works best when you are strictly using ADO and not DAO. On
top of that, it's fast becoming (if it's not already) an ADO world! So, in
the long run you might be better off converting everything to ADO.
As for the databound objects, the answer is: it depends. Some of the
databound objects will work fine, others will produce some of the weirdest
and non-sensical errors you have ever seen :-). I have worked mostly with
the datagrid bound object and found that it was best to ditch it in favor of
re-writing all of the code in ADO. As someone else already stated, the less
complex the application, the better than VB and MySQL will work together.
Otherwise, proceed with caution and get yourself a good ADO reference.
Good Luck,
Dennis
**********************************************
Beridney Computer Services
http://www.beridney.com
----- Original Message -----
From: "Thompson, Mike" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 29, 2001 10:37 AM
Subject: VBA/VB DAO/ADO MS Access to MySQL?
> Howdy,
>
> I currently have an application which uses DAO and ADO coding in VBA/VB as
> well as databound objects in VB to access a MS Access database. Can DAO
and
> ADO in VBA/VB and databound objects in VB be made to work with a MySQL
> database?
>
> Anybody done this successfully?
>
> Cheers,
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
