SQLClient is lightning fast as it talks straight to something callled SQLServer TDS without OLEDB in the middle.
It is closer to "native access". If there was a System.Data.MSAccess library of course using that would be faster than OLEDB to talk to Access but at this time there is not. Stepping back from ccomputers If you could speak French to a French person or translate your English statement to a Spanish statement and have the Spanish person then make the equivalent French statement it is slow and may lead to less quality of translation. OLEDB can talk to many databases and has fat and inneficiency which we tolerate so we can talk to any database with an OLEDB driver. But we oly tolerate it when we have no direct way to talk to the data. On 6/2/05, Tony Trapp <[EMAIL PROTECTED]> wrote: > Hey guys I just wanted to know which is better to use when connecting > to SQL server 2000. > > OleDb or sqlserver > > Which one would you choose and why. > > Thanks guys !! > > Tony... > > > > ________________________________ > Yahoo! Groups Links > > > To visit your group on the web, go to: > http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ > > To unsubscribe from this group, send an email to: > [EMAIL PROTECTED] > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
