Re: Access 2003-Access 2002 Incompatibility
From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 09/05/04
- Previous message: GVaught: "Re: Access 2003-Access 2002 Incompatibility"
- In reply to: GVaught: "Re: Access 2003-Access 2002 Incompatibility"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 5 Sep 2004 06:44:36 -0400
I haven't installed MDAC 2.8 on this machine, but for MDAC 2.7, I see 2
separate references:
Microsoft ActiveX Data Objects 2.7 Library
Microsoft ActiveX Data Objects Recordset 2.7 Library
The first one corresponds to msado15.dll (and adds the ADODB reference),
while the second one corresponds to msador15.dll (and adds the ADOR
reference).
It's my understanding that the most recent version of ADO installed will
always correspond to msado15.dll. If all you've installed is MDAC 2.1, then
Microsoft ActiveX Data Objects 2.1 Library will correspond to msado15.dll.
http://msdn.microsoft.com/library/en-us/odeopg/html/deovradocomponentlibraries.asp
talks about Microsoft ActiveX Data Objects Recordset being "A lightweight
version of ADO that contains only the functionality of the ADO Recordset
object. This version of ADO is typically used only from script in a Web page
to minimize memory requirements."
http://msdn.microsoft.com/library/en-us/vbcon98/html/vbconhowtoreferenceadoinvisualbasic.asp
states:
"To gain access to the ADO 2.0 objects in Visual Basic, set a reference to
the appropriate ADO type library. There are two ADO type libraries. One is
called ADODB and is contained in MSADO15.DLL. It appears in the References
dialog box (available from the Project menu) as "Microsoft ActiveX Data
Objects 2.0 Library". The other is called ADOR and is contained in
MSADOR15.DLL. It appears in the References dialog as "Microsoft ActiveX Data
Objects Recordset 2.0 Library".
"The first type library (ADODB) is the larger and more feature-rich of the
two; it contains the main ADO objects and is the one you'll probably want to
use in most circumstances. The second is a "lightweight" subset of the ADODB
type library that supports only recordsets. You may choose to use that
library instead if you plan to manipulate only recordsets."
-- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "GVaught" <glvaughtRemoveThis@hotmail.com> wrote in message news:OBGGymwkEHA.3152@TK2MSFTNGP12.phx.gbl... > That file name msador15.dll is actually the file name for MDAC 2.8 or at > least on my Win 2K machine. When I opened Access and looked at the reference > list, my ADO 2.8 actually indicates that file name. I thought I was seeing > things, so I looked at ADO 2.7 it actually indicated msado2.7 in the file > name. > > > -- > G Vaught > > > "Brendan Reynolds" <brenreyn at indigo dot ie> wrote in message > news:uXWLihDkEHA.3844@TK2MSFTNGP12.phx.gbl... > > Piggy-backing on Doug's post because I don't see the original ... > > > > msador15.dll is the Microsoft ActiveX Data Objects Recordset library - a > > cut-down version of ADODB intended for use in web applications. I've never > > heard of anyone using it in an Access application. If it is being used at > > all, it can probably be replaced with ADODB, and this would probably solve > > the problem because, unlike ADOR and ADOX, you can have multiple versions > > of > > ADODB installed on one PC. Just leave the reference set to the latest > > version that exists on both PCs. > > > > -- > > 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. > > > > > > "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message > > news:OE9eSJDkEHA.3724@TK2MSFTNGP11.phx.gbl... > >> Have MDAC 2.7 been installed on the machine that's attempting to use the > >> database? > >> > >> -- > >> Doug Steele, Microsoft Access MVP > >> http://I.Am/DougSteele > >> (no e-mails, please!) > >> > >> > >> > >> "Chaplain Doug" <anonymous@discussions.microsoft.com> wrote in message > >> news:418101c49027$f8f50cf0$a601280a@phx.gbl... > >> > I updated an Access 2002 db using Access 2003. Now when I > >> > try to run the db on Access 2002 I get an error message > >> > that says: > >> > > >> > Access contains a missing or broken reference to file > >> > msador15.dll version 2.7 > >> > > >> > What can I do to fix this problem? Or more generally, > >> > what do I do to ensure that dbs created or modified with > >> > Access 2003 will still run on Access 2002? Thanks. > >> > >> > > > > > >
- Previous message: GVaught: "Re: Access 2003-Access 2002 Incompatibility"
- In reply to: GVaught: "Re: Access 2003-Access 2002 Incompatibility"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
