Jim Dettman
jimdettman at earthlink.net
Mon Nov 1 06:57:10 CST 2004
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