be3affb3   
   From: esquel@sommarskog.se   
      
   Emin63 (emin.shopper@gmail.com) writes:   
   > Thanks. I recall having to add DataTypeCompatibility=80 at some point   
   > due to type issues in ADO as you mention. I don't recall why I put in   
   > Driver={SQL Server}. I just did a quick test with a simple query and   
   > things still seem to work fine without it so I will try removing it   
   > and see if that helps. Could the Driver={SQL Server} cause problems?   
      
   It's a little strange that it would only cause problems sometimes.   
      
   > More testing suggests that the intermittent failures may be more   
   > likely to happen when many clients are connecting to the server (which   
   > is sql server 2005) running on a separate machine. I guess it is   
   > possible that this is a network issue. Any thoughts on how to verify   
   > that?   
      
   Intermittent errors are often network problems. But the error message   
   does not point in that direction. It looks like something the OLE DB   
   provider generates before it hits the network. But maybe the API   
   produces an incorrect error code.   
      
      
   --   
   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   
   SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)