Access to MDB's

  • Thread starter Thread starter BobAchgill
  • Start date Start date
B

BobAchgill

What is the best way to get data from an MDB (Access)
file into a Win Form?

And is there a way to do this but not have to install the
H-U-G-E MDAC? (Note: My target users are on Windows 2000
and XP systems.)

My experiences up till now are:

I have been using the Jet driver under OleDbAdapter but I
understand from the MDAC web site that MS stopped
supporting Jet drivers in MDAC 2.6 and later.

I tried the OdbcDataAdapter and that worked but is that
support also going away?

Thanks!

Bob
 
Bob,

My opinion is simple,

ADONET and OleDB

After a reinstall I have never installed MDAC's anymore.

Cor
 
Yes, I have been successful to use this merge module. I
think you told me about it before and it works.

My question is is there a way to get the job done with
out having to install all of the MDAC (5+MB download ->
20MB installed)

I know when I worked with MYSQL database using ODBC the
driver was only 250KB.

Bob
 
To clarify...So your experience is that from a Clean
install of Windows 2000 or XP that you can get ADO.NET +
OleDB to access a MDB file from in a Win Form?? With out
installing MDAC.

Was that using the Jet driver selection? I guess that
would mean that .Net has the Jet driver built in?

I thought I had tried this before but maybe not.

The hard part is to test it because I don't have a clean
machine. Can't unintall MDAC to try it. :o(

Bob
 
On Mon, 17 Jan 2005 00:19:05 -0800, "BobAchgill"

¤ What is the best way to get data from an MDB (Access)
¤ file into a Win Form?
¤
¤ And is there a way to do this but not have to install the
¤ H-U-G-E MDAC? (Note: My target users are on Windows 2000
¤ and XP systems.)
¤
¤ My experiences up till now are:
¤
¤ I have been using the Jet driver under OleDbAdapter but I
¤ understand from the MDAC web site that MS stopped
¤ supporting Jet drivers in MDAC 2.6 and later.
¤
¤ I tried the OdbcDataAdapter and that worked but is that
¤ support also going away?

The underlying technology is still the same. MDAC and Jet are required.

XP comes with Jet 4.0 and MDAC installed. I also seem to recall that MDAC is
installed with .NET Framework 1.1.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
I found this (see link below) which suggest that only ODBC Desktop Pack
drivers ARE included with 2000 and XP operating systems. I guess this
means not Jet.

What are the trades for me switching to using ODBC instead of Jet so I
don't have to have my users install Jet?

Bob

-------------------------------------------------------------------
How to obtain the latest service pack for the Microsoft Jet 4.0
Database Engine
http://support.microsoft.com/kb/239114#9

If you obtain the Jet 4.0 Service Pack 8 download for computers that
are running Microsoft Windows 95, Microsoft Windows 98, and Microsoft
Windows NT version 4.0, you will also receive the ODBC Desktop Driver
Pack drivers. These drivers are included with the Windows 2000
operating system, the Windows XP operating system, and the Windows
Server 2003 operating system. The ODBC Desktop Driver Pack drivers
includes the following files:
 
¤
¤ I found this (see link below) which suggest that only ODBC Desktop Pack
¤ drivers ARE included with 2000 and XP operating systems. I guess this
¤ means not Jet.
¤

I don't see that in the article. AFAIK Jet is installed with XP, but I don't believe it is installed
with 2000.

¤ What are the trades for me switching to using ODBC instead of Jet so I
¤ don't have to have my users install Jet?

The MS Access driver (ODBC) uses the file Msrd3x40.dll which appears to be included w/Jet, not the
ODBC Desktop Driver Pack.


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

To access MBD files from a VB .Net application running on .Net 1.1:

2000 users need to also install Jet 4 for 2000 driver (about 2+MBs)
AND
XP users don't need to install anything more!

Have I got it right?
 
BobAchgill said:
Just to clarify -

To access MBD files from a VB .Net application running on .Net 1.1:

2000 users need to also install Jet 4 for 2000 driver (about 2+MBs)
AND
XP users don't need to install anything more!

Have I got it right?
Click to expand...

AFAIK jet is dao.
OLEDB is ado.
I would think you only need jet if you're using dao.... and I doubt many
people do this in dotnet.

I'd also think:
Say you build a dotnet project uses an mdb
You build an install for it.
Anything that ain't in the framework is supposed to be detected and included
as part of this.
 
¤ Just to clarify -
¤
¤ To access MBD files from a VB .Net application running on .Net 1.1:
¤
¤ 2000 users need to also install Jet 4 for 2000 driver (about 2+MBs)
¤ AND
¤ XP users don't need to install anything more!
¤
¤ Have I got it right?

Sounds correct to me.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Confused about MDAC, VB.Net, and Jet 7
Data Type Mismatch Error 4
Data access requirements - which version(s) of MDAC for Access on Windows 98 2
Redistributable Files For Databases 1
Problem accessing Access database from VB2005 3
Access vs. Wi-Fi 12
MDAC required 3
Accessing MDB's 4

Back
Top