.net - Managed driver for MS Access -


ms access files can read using jet or newer ace. both of these native drivers, i.e. have installed. oracle databases can queried using native drivers (oracle client) or managed .net drivers (odp.net). there such thing managed .net driver ms access?

there managed provider called odbc.net, , been tested sql server, oracle, , access/jet.

however despite being “managed” .net provider, still requires access odbc provider has installed. (so don’t around issue – @ least in case of access). un-managed code driver assumed exist on windows in case of jet.

of course in windows, both sql server , jet providers installed default out of box. in theory not have install additional.

so keep in mind windows includes jet provider can read “mdb” files, not accdb files require install ace database engine.

the above .net “managed” driver works because windows includes un-managed access drivers default.

i not 100% sure of in regards sql server, again suggests managed sql driver works because uses built in un-managed drivers windows provides default. can’t confirm sql server, can access/jet.

so in regards access/jet using un-managed code despite fact of not having install in regards reading mdb files – accdb format files, have include ace connectivity components.

and odbc.net provider while managed code still assumes using defaulted install of un-managed jet drivers mdb files, or in case of "accdb" files, assumed have installed ace drivers. no matter how slice , dice this, might not have install anything, in cases still using un-managed code assumed exist on computer - , means such drivers have match bit size of .net project.


Comments

Popular posts from this blog

angular - Ionic slides - dynamically add slides before and after -

minify - Minimizing css files -

Add a dynamic header in angular 2 http provider -