[AccessD] references and errors

It will use the version of the DAO reference selected,  just as  it will
for XML or ADO (you might have 5 versions of each on a machine)
Just remember DAO 3.6 is Unicode based, so will run slower on Access
97 which is  ANSI based,  you have to perform conversions
DAO 3.51  is ANSI based.
 
Why do you want to confuse the poor wee machine
by selecting both at the same time?


Mark A Matte wrote:

> ">If unchecked then unused. "
>
> This might not be entirely true... according to MS:
>
> http://support.microsoft.com/kb/303829
>
> "In the Microsoft Visual Basic for Applications references, the Data 
> Access Object (DAO) 3.60 Object Library is selected and the DAO 3.51 
> Object Library is not in the list of available references."
>
> This was the case...3.51 was not in the list...but 3.6 was 
> checked...so I copied dao350.dll to the new machine...regestered 
> it...3.51 is still NOT selected but is in the list...3.6 is selected 
> and everything works...
>
> This implies to me that even though 3.6 is selected...3.51 is used 
> somwhere???
>
> Just curious,
>
> 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] references and errors
>> Date: Fri, 02 Mar 2007 09:58:37 -0800
>>
>> If unchecked then unused. It won't let you check both at same time too
>>
>> See Doug Steele's Article
>>
>> Access Reference Problems
>> http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
>>
>> Mark A Matte wrote:
>>
>> > Thanks Marty,
>> >
>> > I also found a site that stated this error would occur if 3.51 was not
>> > an option in the references list...and it was not...so I copied the
>> > dao350.dll to this machine...then used the the code you sent to
>> > register it...I didn't have to check the 3.51 3.6 is checked.  Does
>> > this mean that even though 3.6 is checked...the 3.51 library is used?
>> >
>> > 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] references and errors
>> >> Date: Thu, 01 Mar 2007 14:07:02 -0800
>> >>
>> >> DAO 3.6 is backward compatible with Access 97
>> >> but with a 10% speed drop handling Unicode to ANSI
>> >> conversion. You can use in Access 97
>> >>
>> >> DAO 3.51 cannot read Access 2000 + mdb's
>> >>
>> >> Mark A Matte wrote:
>> >>
>> >> > No...just 97
>> >> >
>> >> >
>> >> >> From: "Charlotte Foust" <cfoust at infostatsystems.com>
>> >> >> 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] references and errors
>> >> >> Date: Thu, 1 Mar 2007 11:18:56 -0800
>> >> >>
>> >> >> CurrentDb is still valid in later versions of Access and DAO, so I
>> >> >> suspect it's something else that is causing the problem.  Does the
>> >> new
>> >> >> machine have a 2003 and 2007 version of Access installed?
>> >> >>
>> >> >> Charlotte Foust
>> >> >>
>> >> >> -----Original Message-----
>> >> >> From: accessd-bounces at databaseadvisors.com
>> >> >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A
>> >> Matte
>> >> >> Sent: Thursday, March 01, 2007 8:53 AM
>> >> >> To: accessd at databaseadvisors.com
>> >> >> Subject: [AccessD] references and errors
>> >> >>
>> >> >> Sorry...forgot to change subject...
>> >> >>
>> >> >> >Hello All,
>> >> >> >
>> >> >> >I have an A97 db that users run reports out of...number of 
>> different
>> >> >> >machines...same db.  New machine won't run of compile...errors on
>> >> "Set
>> >> >> >dbs=CurrentDB".  Error says restricted word or function or uses
>> >> >> >Automation not available in Visual Basic.  The only difference 
>> I can
>> >> >> >see is the new machine has a reference to DAO3.6 and the other
>> >> machines
>> >> >>
>> >> >> >have a DAO3.51 and I can't set a reference to 3.5 on the new
>> >> machine.
>> >> >> >
>> >> >> >Any ideas?
>> >> >> >
>> >> >> >Thanks,
>> >> >> >
>> >> >> >Mark A. Matte
>

-- 
Marty Connelly
Victoria, B.C.
Canada