Using an Access Database in ADO.NET w/o MS Access

[Guest]

If I am using ADO.NET in a VB.NET screen to do inquires, updates, deletes
etc on an MS Access database, does the client or the server that the
application resides on have to have MS Access installed? Or are the MS JET
access routines inherent in the ODBC access methods I'm using?

 

[Jeff Dillon]

Inherent.

 

[Earl]

They might be "inherent in the methods [you] are using" on your development
system, but if you are deploying this application, note that older systems
may not have the correct MDAC version (if any) installed and this could
break your app.

 

[Jeff Dillon]

Um, that is what a setup package is for??

They might be "inherent in the methods [you] are using" on your development
system, but if you are deploying this application, note that older systems
may not have the correct MDAC version (if any) installed and this could
break your app.

If I am using ADO.NET in a VB.NET screen to do inquires, updates, deletes
etc on an MS Access database, does the client or the server that the
application resides on have to have MS Access installed? Or are the MS
JET
access routines inherent in the ODBC access methods I'm using?

 

[Earl]

Yep, just one more item to consider on the deployment. For more fun and
enjoyment, note that the newer MDAC packages may break older unrelated apps.

Um, that is what a setup package is for??

They might be "inherent in the methods [you] are using" on your development
system, but if you are deploying this application, note that older
systems
may not have the correct MDAC version (if any) installed and this could
break your app.

If I am using ADO.NET in a VB.NET screen to do inquires, updates, deletes
etc on an MS Access database, does the client or the server that the
application resides on have to have MS Access installed? Or are the MS
JET
access routines inherent in the ODBC access methods I'm using?

 

[Paul Clement]

¤
¤ If I am using ADO.NET in a VB.NET screen to do inquires, updates, deletes
¤ etc on an MS Access database, does the client or the server that the
¤ application resides on have to have MS Access installed? Or are the MS JET
¤ access routines inherent in the ODBC access methods I'm using?

Microsoft Access does not need to be installed but you will need MDAC and the Jet database engine
components. Depending upon the OS both may be installed. Otherwise, depending on the version you are
using, both will be required:

http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&DisplayLang=en
http://support.microsoft.com/default.aspx?scid=kb;en-us;239114


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)

 

[Jeff Dillon]

That makes no sense. That is the purpose of deployment.

So you are suggesting a better approach is to install a full package of
Access on these problem client machines??

Or are you saying that users that have breakable older apps installed are
simply screwed?

Plus the OP mentioned that the database might be on a server. What exactly
is the environment?

Jeff

Yep, just one more item to consider on the deployment. For more fun and
enjoyment, note that the newer MDAC packages may break older unrelated apps.

Um, that is what a setup package is for??

They might be "inherent in the methods [you] are using" on your development
system, but if you are deploying this application, note that older
systems
may not have the correct MDAC version (if any) installed and this could
break your app.


If I am using ADO.NET in a VB.NET screen to do inquires, updates, deletes
etc on an MS Access database, does the client or the server that the
application resides on have to have MS Access installed? Or are the MS
JET
access routines inherent in the ODBC access methods I'm using?

 

[Earl]

Hehe ... you thought Microsoft always made sense? "Deployment" is installing
YOUR app, eh? Actually, it comes down to "DLL hell", where the version for
an older app will not work with a newer DLL and vice-versa. This issue was
the one (or many) to drive me away from using Access for development.
Particularly if the database is on a server, why not use MSDE or SQL2k.

Here's a nice thread for you to peruse:

http://groups.google.com/groups?hl=...eaking&meta=group%3Dmicrosoft.public.access.*

That makes no sense. That is the purpose of deployment.

So you are suggesting a better approach is to install a full package of
Access on these problem client machines??

Or are you saying that users that have breakable older apps installed are
simply screwed?

Plus the OP mentioned that the database might be on a server. What
exactly
is the environment?

Jeff

Yep, just one more item to consider on the deployment. For more fun and
enjoyment, note that the newer MDAC packages may break older unrelated apps.

Um, that is what a setup package is for??

They might be "inherent in the methods [you] are using" on your
development
system, but if you are deploying this application, note that older
systems
may not have the correct MDAC version (if any) installed and this
could
break your app.


If I am using ADO.NET in a VB.NET screen to do inquires, updates,
deletes
etc on an MS Access database, does the client or the server that the
application resides on have to have MS Access installed? Or are the MS
JET
access routines inherent in the ODBC access methods I'm using?