Email from Bigtnmd:<br><br><b><br>Thanks for your input. I have to connect a dB to a form for class. We have <br>had no instruction on ADO, so your FAQ helped and I will take them back to <br>class today. However, from what you said I could still use DAO, since the <br>application is only for one form and one table, and is my first ever attempt <br>at connection.<br><br>I attend Villa Julie College in Baltimore.<br><br>Thanks,<br>Bigtnmd<br></b><br><br>My response:<br><br><b><br>here is a cut/paste out of the MSDN for DAO<br>"<i><br>What Are DAO and ODBC?<br>Home ¦ Overview ¦ How Do I ¦ FAQ ¦ ODBC Driver List<br><br>Both Data Access Objects (DAO) and Open Database Connectivity (ODBC) are<br>application programming interfaces (APIs) that give you the ability to write<br>applications that are independent of any particular database management<br>system (DBMS).<br><br>DAO is familiar to database programmers using Microsoft Access Basic or<br>Microsoft Visual Basic. DAO uses the Microsoft Jet database engine to<br>provide a set of data access objects: database objects, tabledef and<br>querydef objects, recordset objects, and others. DAO works best with .MDB<br>files like those created by Microsoft Access, but you can also access ODBC<br>data sources through DAO and the Microsoft Jet database engine.<br><br>ODBC provides an API that different database vendors implement via ODBC<br>drivers specific to a particular database management system (DBMS). Your<br>program uses this API to call the ODBC Driver Manager, which passes the<br>calls to the appropriate driver. The driver, in turn, interacts with the<br>DBMS using Structured Query Language (SQL).<br><br>Note As a major part of the Microsoft Windows Open Standards Architecture<br>(WOSA), ODBC is here for the long run. DAO is optimized around the Microsoft<br>Jet database engine, but you can still access ODBC and other external data<br>sources via that engine, and the distinct ODBC API and the MFC classes based<br>on it are still available and still have their role to play in your<br>selection of database tools.<br>"</i><br><br>As you can see it states DAO is oriented around only Jet Databases(usally<br>what the old Access database used to use) , but ADO would seem to be here to<br>stay, as it is suitible for almost all ODBC supported database, specifically<br>Access(2000 and below) and SQL Server, and DAO seems to be getting outdated<br>on the support.<br><br>-Karl<br></b> <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href=
</a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)