odbc vs oledb with access.mdb

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I will be deploying a lot of small websites to various servers. for MSAccess
it seems that odbc is much more convenient because i'd don't need to know the
path to the db. Is there a significant performance difference?
thanks
kes
 
I will be deploying a lot of small websites to various servers. for
MSAccess
it seems that odbc is much more convenient because i'd don't need to know
the
path to the db. Is there a significant performance difference?
Click to expand...

Generally speaking, OleDb will be more "performant", as our American cousins
say, than ODBC.

However, this is probably the least of your worries if you're using Access
as the backend database for a web app...
http://aspalliance.com/14
 
Well, yes, you do need to know the path to the mdb if you're creating
an ASP.NET application that connects to an mdb. You also need to make
sure that you grant the necessary ACLs on the file share where the mdb
and mdw reside so that Access can clean up the ldb files afterwards.
FWIW, Access isn't recommended for web applications due to security
vulnerabilities and general instability. That being said, It is
recommended to use the OleDb provider if you're going to use
Access/Jet as the data store.

--Mary
 
I do agree, access is not the best DB, but..... did you know that ODBC can
be faster then OLEDB as OLEDB is interrop and ODBC is PINVOKE.

in the early days, odbc was faster then native SQL client in certiain
configs.


Steve
 
Back
Top