microsoft dao 2.5/3.5 compatibility library, microsoft dao2.5/3.51 compatibility library, missing microsoft dao 2.5/3.5compatibility library, microsoft excel 16.0 object librarycompatibility, microsoft printer compatibility library, microsoftprinter compatibility library 1.0
microsoft dao 2.5 3.5 compatibility library download
If you are wondering which objects should be disambiguated in VBA code when a database application references both the DAO and ADO libraries, I have a few files included in a Zip archive that you may download here. I have included an Access database which contains a table storing the name of each member of the DAO 3.6 Object Library and the ADO 2.1 Object Library, including the hidden members. The database also contains a query named "Find duplicates for tblADO_DAOObjects." Object names that are present in the recordset of this query should be disambiguated with either ADODB or DAO as a part of the declaration statement in VBA code, so that one does not have to worry about object library priority issues. I have also included an Excel spreadsheet listing all of the members of the DAO 3.6 and ADO 2.1 object libraries, including the hidden members, for handy reference.
Hi All, I have a small database program originally written in Access 95. It ran with very little if any modification of the code, until I tried to remove the old administrative install (on the network drive) of Office 97. Right after that, the program crashes because of a missing reference. The missing reference is "MS DAO 25. 3.5 Compatibility Library." This is a file in the old Office 97 folder. I was able to restore all the old data, and get the program running again, but of course I would like to eliminate the reference to the old library and bring the code up to date. Unfortunately, I've forgotten what little Access coding that I learned for that project, and I'm not sure how to proceed. I notice that there is a help page that mentions unsupported commands with DAO 3.6 and suggests replacements, but I don't think I'm using any of the older commands, although I'm using commands of the same type. I've tried to create a new Access 2000 database, import all the forms and recompile, but running the form gives me a "Compile Error Method or Data Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' I would apreciate a bit of guidance here. Do I need to go learn the new methods and manually rewrite the code? Thanks Jim Helfer WTW Architects Sat, 14 Aug 2004 06:28:56 GMT Chris Mill#2 / 7 MS DAO 2.5/3.5 compatibility Library Any code module, Tools, References, remove the missing reference and check any recommended DAO library should do it. Though there are different versions of DAO libraries, just checking an available one in the References list will usually do it. They are bug fixes and not really code alterations, as far as I know. DAO 3.51 appears to be the standard DAO library for A97. I've no idea what it was for A95, and you'll be hard-pressed to find anyone with experience of A95 here. By all accounts, it was a dog and most people morphed into A97. It's not really clear what you have, "A95 and removing an administrative install of O97". I suggest you remove everything, then decide exactly which version of Office/Access you actually want to install. Few would argue against A97 being better than A95. Chris Quote:> Hi All, > I have a small database program originally written in Access 95. It ran > with very little if any modification of the code, until I tried to remove > the old administrative install (on the network drive) of Office 97. > Right after that, the program crashes because of a missing reference. The > missing reference is "MS DAO 25. 3.5 Compatibility Library." This is a file > in the old Office 97 folder. > I was able to restore all the old data, and get the program running again, > but of course I would like to eliminate the reference to the old library and > bring the code up to date. > Unfortunately, I've forgotten what little Access coding that I learned for > that project, and I'm not sure how to proceed. I notice that there is a > help page that mentions unsupported commands with DAO 3.6 and suggests > replacements, but I don't think I'm using any of the older commands, > although I'm using commands of the same type. > I've tried to create a new Access 2000 database, import all the forms and > recompile, but running the form gives me a "Compile Error Method or Data > Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' > I would apreciate a bit of guidance here. Do I need to go learn the new > methods and manually rewrite the code? > Thanks > Jim Helfer > WTW Architects office_2(); Sat, 14 Aug 2004 07:13:36 GMT Peter Russe#3 / 7 MS DAO 2.5/3.5 compatibility Library Although there could be several issues, the most likely one is that you are using 'dot'notation where 'bang' notation is now required. That is, in Access2 you could reference fields by using things like formname.fieldname but now you have to use formname!fieldname. I am guessing that the compiler is giving you the correct info and you need to plod through the code changing these references. Regards Peter Russell Quote: > Hi All, > Unfortunately, I've forgotten what little Access coding that I > learned for > that project, and I'm not sure how to proceed. I notice that there is a > help page that mentions unsupported commands with DAO 3.6 and suggests > replacements, but I don't think I'm using any of the older commands, > although I'm using commands of the same type. > I've tried to create a new Access 2000 database, import all the forms > and > recompile, but running the form gives me a "Compile Error Method or Data > Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' > I would apreciate a bit of guidance here. Do I need to go learn the > new > methods and manually rewrite the code? > Thanks > Jim Helfer > WTW Architects Sat, 14 Aug 2004 15:04:00 GMT Jim Helfe#4 / 7 MS DAO 2.5/3.5 compatibility Library Quote:> Any code module, Tools, References, remove the missing reference and check any > recommended DAO library should do it. > Though there are different versions of DAO libraries, just checking an > available one in the References list will usually do it. They are bug fixes > and not really code alterations, as far as I know. > DAO 3.51 appears to be the standard DAO library for A97. I've no idea what it > was for A95, and you'll be hard-pressed to find anyone with experience of A95 > here. By all accounts, it was a dog and most people morphed into A97. > It's not really clear what you have, "A95 and removing an administrative > install of O97". I suggest you remove everything, then decide exactly which > version of Office/Access you actually want to install. Few would argue against > A97 being better than A95. > Chris What I meant to say is that I had Office 97 installed to the network folders, and we install users with a lot of "run from network server" options. Turns out that my code needs a reference to the "Microsoft DAO 2.5/3.5 Compatibility Library" that's in F:\apps\MSApps\DAO\DAO2535.tlb Unfortunately, adding the reference to the "Microsoft DAO 3.6 Compatibility Library" didn't help much, so I assume that I'm going to have to update the code to fix this for real. Strangely enough, if I try to unreference the tbl file and move it, and then reference it in a different place, the reference dialog box won't accept it. I can only reference it when it's in the original location. Not sure what that's about. Thanks for your help Jim Helfer WTW Architects Pittsburgh PA - Hide quoted text -- Show quoted text -
> > Hi All, > > I have a small database program originally written in Access 95. It ran > > with very little if any modification of the code, until I tried to remove > > the old administrative install (on the network drive) of Office 97. > > Right after that, the program crashes because of a missing reference. The > > missing reference is "MS DAO 25. 3.5 Compatibility Library." This is a file > > in the old Office 97 folder. > > I was able to restore all the old data, and get the program running again, > > but of course I would like to eliminate the reference to the old library and > > bring the code up to date. > > Unfortunately, I've forgotten what little Access coding that I learned for > > that project, and I'm not sure how to proceed. I notice that there is a > > help page that mentions unsupported commands with DAO 3.6 and suggests > > replacements, but I don't think I'm using any of the older commands, > > although I'm using commands of the same type. > > I've tried to create a new Access 2000 database, import all the forms and > > recompile, but running the form gives me a "Compile Error Method or Data > > Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' > > I would apreciate a bit of guidance here. Do I need to go learn the new > > methods and manually rewrite the code? > > Thanks > > Jim Helfer > > WTW Architects Sun, 15 Aug 2004 05:55:03 GMT office_link(); Jim Helfe#5 / 7 MS DAO 2.5/3.5 compatibility Library Quote:> Although there could be several issues, the most likely one is that you are using 'dot'notation where 'bang' notation is now required. Quote:> That is, in Access2 you could reference fields by using things like formname.fieldname but now you have to use formname!fieldname. Quote:> I am guessing that the compiler is giving you the correct info and you need to plod through the code changing these references. Quote:> Regards > Peter Russell Yuck, I could hardly figure that bang and period stuff out in the first place. Oh well, I guess that's why they pay instead of this being a volunteer effort. Know any good Access books with a cogent explanation of this stuff? Thanks Jim Helfer WTW Architects Pittsburgh PA Quote: > > Hi All, > > Unfortunately, I've forgotten what little Access coding that I > > learned for > > that project, and I'm not sure how to proceed. I notice that there is a > > help page that mentions unsupported commands with DAO 3.6 and suggests > > replacements, but I don't think I'm using any of the older commands, > > although I'm using commands of the same type. > > I've tried to create a new Access 2000 database, import all the forms > > and > > recompile, but running the form gives me a "Compile Error Method or Data > > Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' > > I would apreciate a bit of guidance here. Do I need to go learn the > > new > > methods and manually rewrite the code? > > Thanks > > Jim Helfer > > WTW Architects Sun, 15 Aug 2004 06:57:38 GMT david#6 / 7 MS DAO 2.5/3.5 compatibility Library DAO2535.tlb is only a name/index file. You still have to have dao 3.5 installed. Also, it is registered as HKEY_CLASSES_ROOT\TypeLib\00025E04-0000-0000-C000-000000000046 with a specific location. If you want to move it somewhere else, it has to be re-registered. converting (dot) to (bang) is not that difficult: just convert what Access objects to, and keep going until Access stops complaining. (david) Quote: > > Any code module, Tools, References, remove the missing reference and check > any > > recommended DAO library should do it. > > Though there are different versions of DAO libraries, just checking an > > available one in the References list will usually do it. They are bug > fixes > > and not really code alterations, as far as I know. > > DAO 3.51 appears to be the standard DAO library for A97. I've no idea what > it > > was for A95, and you'll be hard-pressed to find anyone with experience of > A95 > > here. By all accounts, it was a dog and most people morphed into A97. > > It's not really clear what you have, "A95 and removing an administrative > > install of O97". I suggest you remove everything, then decide exactly > which > > version of Office/Access you actually want to install. Few would argue > against > > A97 being better than A95. > > Chris > What I meant to say is that I had Office 97 installed to the network > folders, and we install users with a lot of "run from network server" > options. Turns out that my code needs a reference to the "Microsoft DAO > 2.5/3.5 Compatibility Library" that's in F:\apps\MSApps\DAO\DAO2535.tlb > Unfortunately, adding the reference to the "Microsoft DAO 3.6 Compatibility > Library" didn't help much, so I assume that I'm going to have to update the > code to fix this for real. > Strangely enough, if I try to unreference the tbl file and move it, and > then reference it in a different place, the reference dialog box won't > accept it. I can only reference it when it's in the original location. Not > sure what that's about. > Thanks for your help > Jim Helfer > WTW Architects > Pittsburgh PA > > > Hi All, > > > I have a small database program originally written in Access 95. It > ran > > > with very little if any modification of the code, until I tried to > remove > > > the old administrative install (on the network drive) of Office 97. > > > Right after that, the program crashes because of a missing reference. > The > > > missing reference is "MS DAO 25. 3.5 Compatibility Library." This is a > file > > > in the old Office 97 folder. > > > I was able to restore all the old data, and get the program running > again, > > > but of course I would like to eliminate the reference to the old library > and > > > bring the code up to date. > > > Unfortunately, I've forgotten what little Access coding that I learned > for > > > that project, and I'm not sure how to proceed. I notice that there is a > > > help page that mentions unsupported commands with DAO 3.6 and suggests > > > replacements, but I don't think I'm using any of the older commands, > > > although I'm using commands of the same type. > > > I've tried to create a new Access 2000 database, import all the forms > and > > > recompile, but running the form gives me a "Compile Error Method or Data > > > Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' > > > I would apreciate a bit of guidance here. Do I need to go learn the > new > > > methods and manually rewrite the code? > > > Thanks > > > Jim Helfer > > > WTW Architects Sun, 15 Aug 2004 08:47:33 GMT Chris Mill#7 / 7 MS DAO 2.5/3.5 compatibility Library I'm sorry Jim. I try not to mix versions and I have never had at least these dreaded compatibility problems. If I find they have Officexx, I either supply them with a compatible version of Access or tell them to deinstall everything and start anew. It is clear that you/they have a mess of different versions. As far as I'm concerned, DAO compatibilty libraries can be determined from your development machine, where presumably it works, and distributed with runtime. Chris Quote: > > Any code module, Tools, References, remove the missing reference and check > any > > recommended DAO library should do it. > > Though there are different versions of DAO libraries, just checking an > > available one in the References list will usually do it. They are bug > fixes > > and not really code alterations, as far as I know. > > DAO 3.51 appears to be the standard DAO library for A97. I've no idea what > it > > was for A95, and you'll be hard-pressed to find anyone with experience of > A95 > > here. By all accounts, it was a dog and most people morphed into A97. > > It's not really clear what you have, "A95 and removing an administrative > > install of O97". I suggest you remove everything, then decide exactly > which > > version of Office/Access you actually want to install. Few would argue > against > > A97 being better than A95. > > Chris > What I meant to say is that I had Office 97 installed to the network > folders, and we install users with a lot of "run from network server" > options. Turns out that my code needs a reference to the "Microsoft DAO > 2.5/3.5 Compatibility Library" that's in F:\apps\MSApps\DAO\DAO2535.tlb > Unfortunately, adding the reference to the "Microsoft DAO 3.6 Compatibility > Library" didn't help much, so I assume that I'm going to have to update the > code to fix this for real. > Strangely enough, if I try to unreference the tbl file and move it, and > then reference it in a different place, the reference dialog box won't > accept it. I can only reference it when it's in the original location. Not > sure what that's about. > Thanks for your help > Jim Helfer > WTW Architects > Pittsburgh PA > > > Hi All, > > > I have a small database program originally written in Access 95. It > ran > > > with very little if any modification of the code, until I tried to > remove > > > the old administrative install (on the network drive) of Office 97. > > > Right after that, the program crashes because of a missing reference. > The > > > missing reference is "MS DAO 25. 3.5 Compatibility Library." This is a > file > > > in the old Office 97 folder. > > > I was able to restore all the old data, and get the program running > again, > > > but of course I would like to eliminate the reference to the old library > and > > > bring the code up to date. > > > Unfortunately, I've forgotten what little Access coding that I learned > for > > > that project, and I'm not sure how to proceed. I notice that there is a > > > help page that mentions unsupported commands with DAO 3.6 and suggests > > > replacements, but I don't think I'm using any of the older commands, > > > although I'm using commands of the same type. > > > I've tried to create a new Access 2000 database, import all the forms > and > > > recompile, but running the form gives me a "Compile Error Method or Data > > > Member not found" on 'gUpdateMonth = Updateset.UpdateMonth' > > > I would apreciate a bit of guidance here. Do I need to go learn the > new > > > methods and manually rewrite the code? > > > Thanks > > > Jim Helfer > > > WTW Architects Sun, 15 Aug 2004 08:46:45 GMT Page 1 of 1 [ 7 post ] Relevant Pages 1. Access DAO 2.5/3.5 Compatibility Library
2ff7e9595c
Comentarios