DAO 3.6 needs to be high up in the reference priorty. On my development
machine, it is as high as possible. When I install my database application
on another machine, sometimes ( but not always) it drops down to the bottom
of the list, causing compile and other problems. I never know whether it
will happen or not.

Has anyone seen this, and what to do about it.

Thanks,
Rich

The order should not change.

In any case, you could solve the issues with:
1. Remove any references you don't need.
If you are not sure which references you need for your version of Access,
see:
http://allenbrowne.com/ser-38.html
Ideally get it down to just 3.

2. Explicitly disambiguate any objects that are found in multiple libraries.
For example, instead of:
Dim rs As Recordset
use:
Dim rs As DAO.Recordset
Then it doesn't matter which library has higher priority.

You can do this application-wide for an existing app, by replacing:
As Recordset
with:
As DAO.Recordset
Other objects that need explicit declaration include Field, Property,
Parameter (and the plurals of these.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Rich Schoenfeld" <(E-Mail Removed)> wrote in message
news:WMjAf.3145$(E-Mail Removed)...
> DAO 3.6 needs to be high up in the reference priorty. On my development
> machine, it is as high as possible. When I install my database
> application on another machine, sometimes ( but not always) it drops down
> to the bottom of the list, causing compile and other problems. I never
> know whether it will happen or not.

The problem is that I have some third-party controls that I need to
reference. And the DAO does move to the bottom ...

How do I prevent it from moving to the bottom.


"Allen Browne" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The order should not change.
>
> In any case, you could solve the issues with:
> 1. Remove any references you don't need.
> If you are not sure which references you need for your version of Access,
> see:
> http://allenbrowne.com/ser-38.html
> Ideally get it down to just 3.
>
> 2. Explicitly disambiguate any objects that are found in multiple
> libraries.
> For example, instead of:
> Dim rs As Recordset
> use:
> Dim rs As DAO.Recordset
> Then it doesn't matter which library has higher priority.
>
> You can do this application-wide for an existing app, by replacing:
> As Recordset
> with:
> As DAO.Recordset
> Other objects that need explicit declaration include Field, Property,
> Parameter (and the plurals of these.)
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Rich Schoenfeld" <(E-Mail Removed)> wrote in message
> news:WMjAf.3145$(E-Mail Removed)...
>> DAO 3.6 needs to be high up in the reference priorty. On my development
>> machine, it is as high as possible. When I install my database
>> application on another machine, sometimes ( but not always) it drops down
>> to the bottom of the list, causing compile and other problems. I never
>> know whether it will happen or not.
>
>

The presence of some other references is not the cause of the problem. I
don't understand why it is moving to the bottom. Setting references in code
is a bit of a dog's breakfast. Best article I can suggest:
http://www.trigeminal.com/usenet/usenet026.asp?1033

Explicitly disambiguating should solve the problem with the code.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Rich Schoenfeld" <(E-Mail Removed)> wrote in message
news:M0AAf.3492$(E-Mail Removed)...
> The problem is that I have some third-party controls that I need to
> reference. And the DAO does move to the bottom ...
>
> How do I prevent it from moving to the bottom.
>
>
> "Allen Browne" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> The order should not change.
>>
>> In any case, you could solve the issues with:
>> 1. Remove any references you don't need.
>> If you are not sure which references you need for your version of Access,
>> see:
>> http://allenbrowne.com/ser-38.html
>> Ideally get it down to just 3.
>>
>> 2. Explicitly disambiguate any objects that are found in multiple
>> libraries.
>> For example, instead of:
>> Dim rs As Recordset
>> use:
>> Dim rs As DAO.Recordset
>> Then it doesn't matter which library has higher priority.
>>
>> You can do this application-wide for an existing app, by replacing:
>> As Recordset
>> with:
>> As DAO.Recordset
>> Other objects that need explicit declaration include Field, Property,
>> Parameter (and the plurals of these.)
>>
>> "Rich Schoenfeld" <(E-Mail Removed)> wrote in message
>> news:WMjAf.3145$(E-Mail Removed)...
>>> DAO 3.6 needs to be high up in the reference priorty. On my development
>>> machine, it is as high as possible. When I install my database
>>> application on another machine, sometimes ( but not always) it drops
>>> down to the bottom of the list, causing compile and other problems. I
>>> never know whether it will happen or not.