The application we develop here at icarz was written using MyODBC and ADO ... I
wrote the MyVbQL API to replace the use of ADO in our application with minimal
code changes ... The names and functionality of most of the methods and
properties are modeled after ADO methods and properties ... Anyone using ADO
should be able to make a transition to MyVbQL very easily ... Plus since it uses
libmysql.dll you also get the extra functionality and flexibility that
libmysql.dll provides ...
Eric
http://www.icarz.com/mysql/index.html
> ADO plusses: flexible and simple to code (few objects), easy to port and
> support in the future
> ADO minuses: Adds a layer of processing, therefor slower
> API plusses: speed
> API minuses: Yet another API to learn (however, it might be as easy as ADO,
> I don't know)
---------------------------------------------------------------------
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
