Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Microsoft JET OleDb driver
Message
From
09/05/2013 18:41:14
 
 
To
09/05/2013 18:21:15
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01573051
Message ID:
01573339
Views:
52
I can't say it's faster nor can I say it isn't supported (yet).

Case in point... several years ago I did some timing tests in VFP to access SQL Server. I used SQL Passthrough (ODBC), ADO (OLEDB), and cursor adapter (ODBC & ADO). Some things were faster with ODBC, some faster with OLEDB, some with SPT, some with CA. Bottom line, the speed depends on what you are doing. Of course it could be entirely different with non-SQL Server connections as they would use different ODBC drivers or OLEDB providers.


>So, I assume the vote would be to use the ODBC, because the prime reason is that it is faster and supported, which will not be the case soon with the OleDb provider. Thus, this means we would compile in 32 bits for that single project.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform