Re: Cannot connect ADO to MS Access 2000
From: Jim Rodgers (noway_at_jose.com)
Date: 12/07/04
- Next message: Adam: "ADO 2.5(Is database ReadOnly)"
- Previous message: Somebody: "Re: Trying to do a seek on a Key that is a Long and Date field"
- In reply to: Brendan Reynolds: "Re: Cannot connect ADO to MS Access 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 7 Dec 2004 16:11:10 -0500
Dear "very new to VB6,"
Often you will find you need some update or another to make something work
-- and this is especially true of MDB file-based applications. Also, you
often
will find the files can be obtained from more one update. Finally, you may
need
files that cannot all be found in one update. Exactly which updates depends
on
which versions you have vis-a-vis Windows OS, which Windows SP, which
MS Office, which Office SP, which Visual Studio (or VB), and which SP for
that, etc., etc. (By the way, your VB should now be at SP6.)
UPDATING YOUR VB DEVELOPMENT PC
In addition to the latest updates, some of which are truly needed, you will
need
to make the correct references in your VB6 program. On the menu select
Project /References and select "Microsoft ActiveX Data Objects 2.8 Library"
at the minimum. Depending on your program, you may also need references to
the following:
Microsoft Data Binding Collection VB6 (SP4)
Microsoft Data Source Interfaces
Microsoft Data Formatting Object Library 6.0 (SP6)
Microsoft Jet and Replication Objects 2.6 Library
Microsoft ADO Ext. 2.8 for DDL and Security
Regarding updates, first you will want the latest "MDAC" installation.
Next,
there is an update called Jet 4.0 SP8 that would be good to have installed
on
your PC to help make sure things are working okay. Also, if you are using
Jet 3.5, then there is an update for Jet 3.51 you need to prevent crashes.
If
you do Repair or Compact database from your VB6 program, you will need
the JRO update (Jet and Replication Objects) and project reference. If you
have Windows 98, you should make sure you have installed the DCOM98
update.
UPDATING YOUR CUSTOMERS' PCs
Generally, you may need to install certain updates on your customer's PC if
you have them on your development PC. When you reference items in VB6
(like those above), the VB6 Package and Deployment Wizard (PDW) will
include them in the setup files (in the .CAB file). In the PDW, you can
specify
that these files should be downloaded from a Microsoft website instead of
the
CAB file -- if you would like. Certain items are, by default, configured
that
way because Microsoft can on the fly adjust which exact file to install on
the
customer's PC. The latest file for your Win2k server may not be the correct
file to use on a customer' WinXP Pro PC. Besides, why include all those
DLLs
if you don't need to? (Because not everyone has Internet access, that's
why.)
SUMMARY
Here is a summary I just cut-n-pasted from the comments section of one of
my applications that use MDB files:
MDAC 2.5 installs the same components as Windows 2000 SP3.
MDAC 2.8 installs the same components as Windows Server 2003.
MDAC 2.5 is the *** LAST **** mdac to install MSJET and MSJRO
components. It is "supported" by Win95 (w/DCOM95), Win98, NT4SP3
and later, and MSIE 3.01 and later.
MDAC 2.8 includes ADO 2.8 and Microsoft SQL ServerT OLE DB
provider and ODBC driver. It is "supported" by Windows 2003, Win2k,
98, ME, NT, and XP.
Suggested data technologies install SEQUENCE for Win98 (worst-case) is...
1. DCOM98
2. MDAC 2.5 SP3
3. MDAC 2.8 (or later)
4. MSJET 3.51 update
5. MSJET 4.0 update (latest available)
6. MSJRO update
7. [Re-] Install MSIE 6.0 or later.
Available MSJET 4.0 Updates...
Jet40SP7_WMe.exe
Jet40SP8_9xNT.exe
Windows2000-KB829558-x86-ENU.exe
WindowsServer2003-KB829558-x86-ENU.exe
WindowsXP-KB829558-x86-ENU.exe
Good luck!!
"Brendan Reynolds" <brenreyn at indigo dot ie> wrote in message
news:uSLQLdH3EHA.1188@tk2msftngp13.phx.gbl...
> If the *only* thing that has changed is the version of Access used to
create
> the MDB, then probably the only thing you need to change is the version of
> the Jet OLEDB provider. You need to use the 4.0 provider instead of the
3.51
> provider, if you haven't already done so.
>
> If that doesn't work for you, or if you've already done that, try posting
> the connection string you're using and telling us what happens when you
> attempt to use it.
>
> --
> Brendan Reynolds (MVP)
> http://brenreyn.blogspot.com
>
> The spammers and script-kiddies have succeeded in making it impossible for
> me to use a real e-mail address in public newsgroups. E-mail replies to
> this post will be deleted without being read. Any e-mail claiming to be
> from brenreyn at indigo dot ie that is not digitally signed by me with a
> GlobalSign digital certificate is a forgery and should be deleted without
> being read. Follow-up questions should in general be posted to the
> newsgroup, but if you have a good reason to send me e-mail, you'll find
> a useable e-mail address at the URL above.
>
>
> "eyesl" <eyesl@discussions.microsoft.com> wrote in message
> news:57A452FF-B6BA-4E50-AFB6-A5E88DCD193D@microsoft.com...
> > Please help, I am very new to VB6.
> >
> > I was previously working with earlier versions of MS access with VB6.
It
> > was working fine until i started using MS access 2000. What is the
> > problem.
> > What do i need to do to make it work.
> >
> > Thanks.
>
>
- Next message: Adam: "ADO 2.5(Is database ReadOnly)"
- Previous message: Somebody: "Re: Trying to do a seek on a Key that is a Long and Date field"
- In reply to: Brendan Reynolds: "Re: Cannot connect ADO to MS Access 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
