Jim Lawrence (AccessD)
accessd at shaw.ca
Mon Nov 1 21:03:16 CST 2004
Hi Borge: Try something like: c:\MyWindowsDirectory\(system or system32)\regsrv32 -u DAO360.DLL to check that is removed or not improperly registered and then c:\MyWindowsDirectory\(system or system32)\regsrv32 C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL To register the dll. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Borge Steen Hansen Sent: Monday, November 01, 2004 5:14 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] CurrentDB Error The DAO reference is not broken. Reference is to Microsoft DAO 3.6 Object library The actual file is C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL Since the Access97 apps have been stable for a long time, my line of thinking is that some how the DAO360.DLL file has been updated either by installed another program, doing a microsoft update etc. So I searched all instances of DAO360.dll and placed an earlier build version in the folder. Same result. I have now compared similar Access97 application installed on another WinXP box. These apps have reference to DAO3.51 So somehow at some point what must have happened on the problem workstation is similar to what is described by Microsoft in one of their KB articles. Microsoft KB303829 describes the occurrance of exactly this error message (Compile Error: Function or interface marked as restricted, or the function uses Automation type not supported in Visual Basic.) after having updated the workstation to Microsoft Windows 2000. Here's the article pointer: http://support.microsoft.com/default.aspx?scid=kb;en-us;303829 In a nutshell: When installing Windows 2000 an Access97 gets into trouble: "because during Windows2000 installation, the windows registry registers DAO3.60 and updates the reference in Access97 to DAO 3.60. Windows also removes the registration for DAO3.51" Nice eh? Really .... nice!! Microsoft's suggested action is to register DAO3.51 again using the regsvr32.exe Now, what I'd like to know is : Is DAO3.60 not compatible with Access97 Should you only use DAO3.51 ?? Secondly, how do you register DAO3.51 back into the registry?? I cannot use regsrv32 on WinXP. Is this another subtle attempt by Microsoft to abandon older M$ software? Enough! In summary: Can some one please give me the recipe for registering DAO3.51 in WinXP? Regards Borge Gold Coast, Australia ----- Original Message ----- From: "Jim Dettman" <jimdettman at earthlink.net> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Monday, November 01, 2004 10:57 PM Subject: RE: [AccessD] CurrentDB Error > > The DAO reference may be broken. Open a module in design view, click > tools/references. See if it's listed as MISSING or BROKEN. If it is, most > likely you'll simply need to re-register it with regsvr32.exe > > I none are listed missing or broken, check any reference that is not > currently checked, close the MDB and Access, re-open and uncheck the > reference you just checked. Then try a compile. > > Jim Dettman > (315) 699-3443 > jimdettman at earthlink.net > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Borge Steen > Hansen > Sent: Sunday, October 31, 2004 9:51 PM > To: accessd at databaseadvisors.com > Subject: [AccessD] CurrentDB Error > > > Hi, > I have a some Access97 database applications that have been working for > years. > They are currently sitting on WinXP with AccessXP installed as well. > > Been working on the XP box for over a year! > > Recently when making a minor modification and doing a 'Compile and Save' I > get the following message on the first instance of CurrentDb > > Compile Error: > Funtion or interface marked as restricted, or the function uses Automation > type not supported in Visual Basic. > > I have reference to Microsoft DAO Object Library 3.6 > The dao.dll is version 03.60.8618.0 > > Even if I try to disambiguate the thing, the compile error comes up: > > like: > > dim db as DAO.Database > set db = CurrentDb > > when compiling it will error on the set db = CurrentDb line. > > Can anyone help me to shed light on what is going on? > > > Regards > Borge > Gold Coast, Australia > > > --- > Outgoing mail is certified Virus Free by AVG Anti Virus System. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.773 / Virus Database: 520 - Release Date: 5/10/2004 > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com --- Outgoing mail is certified Virus Free by AVG Anti Virus System. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.773 / Virus Database: 520 - Release Date: 5/10/2004 -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com