Check the references again, against a working machine. The references don't
only have to be there, they must be in the same order of priority. Her
machine may have the references in different order to priority.
HTH
>Hi TWIMC
>
[quoted text clipped - 58 lines]
>TIA
>KM

Signature
Sam
Kevin McCartney - 28 Nov 2005 14:35 GMT
Hi
I can't see the order of references having any relevance to the error, is
the an MSDN web site that highlights this issue of having reference in a
preference order?
TIA
KM
> Check the references again, against a working machine. The references don't
> only have to be there, they must be in the same order of priority. Her
[quoted text clipped - 64 lines]
> >TIA
> >KM
Kevin McCartney - 28 Nov 2005 14:37 GMT
In addition the references are in alphabetical order so you can sort them
anyway!
> Check the references again, against a working machine. The references don't
> only have to be there, they must be in the same order of priority. Her
[quoted text clipped - 64 lines]
> >TIA
> >KM
OfficeDev18 - 28 Nov 2005 15:32 GMT
I'm not sure if you and I are referring to the same references. With the new
user's VBA editor open, click on Tools-->References. The order of references
is critical, as this determines the order that Access tries to fulfill the
VBA commands. For example, if you use DAO objects/code and you have the ADO
reference above the DAO reference, your program will bomb. This is why
there's a huge 'UP' and 'DOWN' arrow in the dialog box, to position the
references precisely where you need them. That's why I'm telling you to check
her ref's against a known working machine. Her reference order may not match,
and that's a possible reason for your problem.
>In addition the references are in alphabetical order so you can sort them
>anyway!
[quoted text clipped - 4 lines]
>> >TIA
>> >KM

Signature
Sam