[AccessD] Compile Error A97

Office 97 SP2...not sure the JET.  I tried to create a new DB on these 
machines...and get the same error.  as the business has moved on...I think 
I'll let this one go.

Thanks,

Mark A. Matte


>From: MartyConnelly <martyconnelly at shaw.ca>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Compile Error A97
>Date: Mon, 26 Jun 2006 12:13:01 -0700
>
>Are you running with Office 97 SP2 and Jet SP 8.0
>The last mod to DAO 3.5 was Jet SP4.0 or 3.0 and is not inclusive
>with Jet SP 8.0 mods.
>WinXP comes with MDAC 2.7 which has no DAO Jet components.
>Without a decompile or import all objects to a new 97 mdb and a compile
>all after removing DAO 3.5, you could have references in p-code
>still pointing at old Dao 3.5 code.
>I would run a copy of Belarc and see if you can identify the
>installed software version differences on the machines.
>
>
>Mark A Matte wrote:
>
> >Thanks to everyone that helped...nothing works...but the computers are
> >consistently breaking on a specific line  (currentDB).  We have concluded
> >that this issue is caused by the 'build' on these machines.  For
> >example...new person comes to work...their job is "XYZ Counter"...IT gets
> >them a computer and loads it with "XYZ Counter" build(all apps needed for
> >this job bundled into 1 ).
> >
> >When they create these builds they mix/match/pair/share dlls and other 
>files
> >needed to run an application.  Apparently there is a conflict with some 
>of
> >the dlls...we will have to change the build to correct the issue.
> >
> >Here's where the beauty of big business shines...Solution: "We just won't
> >use the app on those machines...problem solved."
> >
> >Bottom line...I get a pat on the back for a db that doesn't work on most 
>of
> >the machines here.
> >
> >Hope everyone else is having a great day!!!
> >
> >Mark A. Matte
> >
> >
> >
> >
> >>From: "StaRKeY" <starkey at wanadoo.nl>
> >>Reply-To: Access Developers discussion and problem
> >>solving<accessd at databaseadvisors.com>
> >>To: "'Access Developers discussion and problem
> >>solving'"<accessd at databaseadvisors.com>
> >>Subject: Re: [AccessD] Compile Error A97
> >>Date: Sat, 24 Jun 2006 11:50:53 +0200
> >>
> >>Hi Mark,
> >>
> >>I had the same problem with a customer, once the 1st line like you
> >>mentioned
> >>set db=currentdb() does not work the problem is almost certain the
> >>installation of MS Office/Access... Once MS Access/Office had been
> >>re-installed all worked fine again.
> >>
> >>You could also try a 'decompile' and a compile (having dao 3.6 
>referenced)
> >>
> >>Run... "C:\program files\microsoft office\office\msaccess.exe"
> >>"c:\yourapp.mdb" /decompile
> >>
> >>Or if this does not help, try importing all objects in a new database
> >>created on the new machine. My guess though is that is has to do with 
>the
> >>MS
> >>Access on the other machines.... One way to find out is to create a new 
>mdb
> >>on the other machine then open a new module, set a ref to dao3.6 and in 
>the
> >>immediate window type '?currentdb.name' (without the ''). If you get an
> >>error something is wrong with the installed Access version or the VBA
> >>dll's.
> >>
> >>
> >>Regards,
> >>Eric
> >>
> >>-----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 8: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
> >>
> >>
> >>
> >>
>
>--
>Marty Connelly
>Victoria, B.C.
>Canada
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com