From: esquel@sommarskog.se   
      
   Jason Keats (jkeats@melbpcDeleteThis.org.au) writes:   
   > However, Microsoft created DAO, RDO and ADO for a reason. These   
   > high-level COM APIs wrap ODBC to make life easier,   
      
   ADO sits on top of OLE DB. And whether ADO really made life easier can   
   be disputed. I've spent quite some time trying to find out what ADO is   
   really doing, and helping people who were just confused. Not talking about   
   fighting some awfully horrible bugs. (ADO may decide - without reason - that   
   it needs to know the metadata of the result set coming back, so it issues   
   "SET FMTONLY ON EXEC some_sp SET FMTONLY OFF". Unfortunately, the stored   
   procedure results in an error when FMTONLY is ON, and this is an error of   
   the kind that rolls back the transaction. ADO drops this error on the   
   floor.)   
      
   True, using naked OLE DB is certainly tedious, but at least you have   
   control. And that's OLE DB. ODBC is somewhat less tedious to work with, I   
   believe. (I have not programmed much with ODBC.)   
      
   And speaking of OLE DB vs. OBDC, Microsoft has deprecated OLE DB as a   
   connection mechanism to SQL Server. And MSDASQL + ODBC has been deprecated   
   as a connection mechanism for a long time.   
      
   And today if you write native code, I would assume that your language is   
   C++, where ODBC rather fits better than ADO.   
      
   > But, for anyone using ADO (and not the ODBC API), the solution is not to   
   > use incompatible data types in your database! :-)   
   >   
      
   Right. The solution is to switch to an API that gives full support for   
   what the database exposes.   
      
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)