I believe that the OLEDB classes go through COM Interop. When hitting a SQL Server database, SqlClient is the best choice.

-Mike

>The main difference will be performance. Supposedly (I haven't really tested this) the SqlClient provider is much faster at passing and retrieving data from SQL server...
>
>Now I would suggest you shouldn't worry about this in your app and instead create a data access layer that can hand you back the right kind of Connection, DataAdapter and Command objects as interface refs rather than concrete class objects. That way you can easily switch between ADO/SQL and whatever other drivers there are out there without giving up the benefits of each architecture.
>
>+++ Rick ---
>
>
>>Hello to everybody!
>>
>>Can somebody tell me the (dis-)advantages of using ado or sqlconnection.
>>
>>The reason for this (something stupid) question is that I want to create a web application with a sql-server in the background and I prefer sqlconnection but my college prefers ado.
>>
>>We do know the basic differences but only theoretically.
>>We are not able to decide what's the best to use. But I'm sure you can tell me or give me a hint where I can find in-depth info.
>>
>>TIA