From: esquel@sommarskog.se   
      
   Jason Keats (jkeats@melbpcDeleteThis.org.au) writes:   
   > Erland Sommarskog wrote:   
   >> Jason Keats (jkeats@melbpcDeleteThis.org.au) writes:   
   >>> It looks like its time to drop VB6 and ADO and move to C++ and ODBC. ;-)   
   >>>   
   >>   
   >> Or .Net. There is still room for native code - SQL Server is full of   
   >> that - but the applications that are in native code because they should   
   >> be were rarely implemented in VB6.   
   >   
   > That was supposed to be a joke, Erland. I doubt very much that I'll ever   
   > use C++ or ODBC (directly). I am using .NET on the server. It's just   
   > unfortunate that Microsoft doesn't have a good (ie, not C++) native code   
   > replacement for VB6.   
      
   Admittedly, I am outside my expertise, but if you want native code because   
   managed code has too much overhead, why would want something like VB6?   
      
   C++ may look more scary than VB6, but given that C++ has inheritance   
   and VB6 does not, I am not sure that VB6 is overall more productive   
   for what you would write in native code today.   
      
      
      
   --   
   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)