8d022a3f   
   From: esquel@sommarskog.se   
      
   Zabuti Maxim (zabutimaxim@gmail.com) writes:   
   > Well instead of parse tcp packets, I prefer to develop OLE DB   
   > provider, but I thought maybe there is some way to hook it in easier   
   > way.   
      
   Developing an OLE DB is neither that trivial, but it's certainly doable.   
   And if your application uses OleDb client you might even be able to   
   persuade it to use your OLE DB provider.   
      
   But presunably the application uses SqlClient (well, it should). I don't   
   know, may you can write your own .Net Data Provider, and lure the   
   application to use it, but that would require quite some hacking. The   
   people in micrsoft.public.dotnet.framework.dotnet may have more   
   information.   
      
      
      
   --   
   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)