Lonnie Johnson
prodevmg at yahoo.com
Mon Nov 1 01:10:12 CST 2004
Were you doing some ADO programming with AccessXP and moved the ADO reference above the DAO? I have seen that happen before and caused problems. Just a thought. Borge Steen Hansen <pcs at azizaz.com> wrote: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 May God bless you beyond your imagination! Lonnie Johnson ProDev, Professional Development of MS Access Databases Visit me at ==> http://www.prodev.us --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish.