>It still begs the question, "Am I as good as I think I am..." < bg >

Yup. The problem is even more difficult now! :)

>Actually, I chose VB because I know get paid by the number of lines of code..< bg >

Ok. So I *derive* from here that you still didn't understand the problem with the inheritance... :)

>ADO is not based on ODBC. First off, it is important to separate ADO from OLE-DB. ADO is a set of high-level interfaces that provide access to a set of low-level interfaces in OLE-DB. Everything ADO can do is determined by the specific OLE-DB Provider used. There are several OLE-DB Providers available including those for SQL-Server, Oracle, Directory Services, OLAP, Remote Data Services, Etc. There is also an OLE-DB Provider for ODBC. This allows folks who depend on ODBC to make use of ADO. In the case of VFP data, we need to use this provider. If you are using SQL-Server on the other hand, you can bypass, and you should, ODBC entirely.

Thanks. This is what I was thinking. But the that speaker was so sure about it and it said it so many times... Maybe I didn't really understand what he wanted to say. But I doubt it. He also had a very clear picture where OleDB was on top of ODBC and ADO on top of OLEDB. Thanks again. Is there any "to be continued" to your article?

Vlad