Accessing Ms Access

  • Thread starter Thread starter Frank Rizzo
  • Start date Start date
F

Frank Rizzo

Is there a native .NET provider for Jet (mdb, access, whatever it is
called today). It seems that accessing it through OLEDB Jet Provider is
kind of inefficient.

Thanks.
 
Hi Frank,

I don't there is any. Why do you find it inefficient?
Don't forget that it was mostly used through OleDb even before...
 
Miha said:
Hi Frank,

I don't there is any. Why do you find it inefficient?
Don't forget that it was mostly used through OleDb even before...
Click to expand...

The tremendous COM interop going on in the background. One can access
it much faster via ODBC namespace since it is mostly P-Invoke which is
faster.

But a .NET provider would be much better.
 
Hi Frank,

I am not sure about COM interop part.
OleDb can me also P-Invoked, though I don't know if this is the case with
ADO.NET.
I suppose they've choosen the faster way.
Why don't you choose MSDE rather if that is the issue?
 
Miha said:
Hi Frank,

I am not sure about COM interop part.
OleDb can me also P-Invoked, though I don't know if this is the case with
ADO.NET.
Click to expand...

The OleDb Client provider is all interop because it requires MDAC 2.7,
which is COM based.
I suppose they've choosen the faster way.
Why don't you choose MSDE rather if that is the issue?
Click to expand...

The distribution is a pain.
 
¤ Is there a native .NET provider for Jet (mdb, access, whatever it is
¤ called today). It seems that accessing it through OLEDB Jet Provider is
¤ kind of inefficient.

No, although I'm curious what kind of performance problems you would experiencing.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Paul said:
¤ Is there a native .NET provider for Jet (mdb, access, whatever it is
¤ called today). It seems that accessing it through OLEDB Jet Provider is
¤ kind of inefficient.

No, although I'm curious what kind of performance problems you would experiencing.
Click to expand...

I am not sure whether it is the interop, the OLEDB Client provider or
the .NET framework itself, but it just feels slower than vb6 and ado.
I'll investigate further.
 
Back
Top