O'Connor, Patricia (OTDA)
Patricia.O'Connor at otda.state.ny.us
Fri Jun 23 16:30:53 CDT 2006
This might help http://support.microsoft.com/?scid=kb;en-us;887033&spid=2509&sid=49 ************************************************** * Patricia O'Connor * Associate Computer Programmer Analyst * OTDA - BDMA * (W) mailto:Patricia.O'Connor at otda.state.ny.us * (w) mailto:aa1160 at nysemail.state.ny.us ************************************************** > -------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > Mark A Matte > Sent: Friday, June 23, 2006 02:49 PM > To: accessd at databaseadvisors.com > Subject: [AccessD] Compile Error A97 > > Hello All, > > In A97 I built a db...runs fine on my machine...pu it on > other machines(same OS same Access Version) and get the > following: Compile error: Function or Interface marked as > restricted, or the function uses an Automation type not > supported in Visual Basic. > > There are no missing references...the only difference I can > find is I have a reference to DAO 3.51 and they have DAO 3.6 > I change mine to DAO 3.6 and it still runs. This seems to be > the case on all of the machines in the office I have tested. > The 1 line it does NOT > like seems to be " Set db = CurrentDb()". > > Any ideas on how to fix from a coding standpoint? > > Thanks, > > Mark A. Matte > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >