ADO Not Working in Run Time Version

[George W. Jackson]

Hi to all.


We have a Microsoft Access 2002 database that is referencing the
ADO 2.5 library (as well as the DAO 3.6 library). On the development
machine, the database works exactly as planned and all functions
compile and work. When the database is packaged as a runtime version,
and installed on another machine,
errors occur relating to the ADO library, such as the DATE() function
no longer working. (Yes, ADO is being installed as part of the
package!)

Now, here is the odd part; we can put the database on a machine
with a full version of Access and the same ADO errors occur, but if we
un-reference ADO and compile the modules, then re-reference ADO and
compile again, everything starts working correctly. We have checked
the order of referenced libraries; have tried the ADO 2.7 library;
nothing seems to make any difference. We know it is somehow related to
ADO and have checked and installed the same versions of MDAC on the
various machines (all of which are running Windows XP Pro). What are
we missing and as a work-around in the meantime, is there any way to
reference or un-reference libraries under the runtime version of
Access.

We are in major need of help, please. I would greatly appreciate any
help that is given.

Sincerely,



G. Jackson

[Lyle Fairfield]

Re: ADO Not Working in Run Time Version

jacksonbilly@ho tmail.com (George W. Jackson) wrote in
news:47c1d936.0 310160917.15491 70a@posting.goo gle.com:
[color=blue]
> Hi to all.
>
>
> We have a Microsoft Access 2002 database that is referencing the
> ADO 2.5 library (as well as the DAO 3.6 library). On the development
> machine, the database works exactly as planned and all functions
> compile and work. When the database is packaged as a runtime version,
> and installed on another machine,
> errors occur relating to the ADO library, such as the DATE() function
> no longer working. (Yes, ADO is being installed as part of the
> package!)
>
> Now, here is the odd part; we can put the database on a machine
> with a full version of Access and the same ADO errors occur, but if we
> un-reference ADO and compile the modules, then re-reference ADO and
> compile again, everything starts working correctly. We have checked
> the order of referenced libraries; have tried the ADO 2.7 library;
> nothing seems to make any difference. We know it is somehow related to
> ADO and have checked and installed the same versions of MDAC on the
> various machines (all of which are running Windows XP Pro). What are
> we missing and as a work-around in the meantime, is there any way to
> reference or un-reference libraries under the runtime version of
> Access.
>
> We are in major need of help, please. I would greatly appreciate any
> help that is given.[/color]

If you think ADO and MDAC are the cause of the problem then you might try
running ComCheck
<http://support.microsoft.com/default.aspx?
scid=http://support.microso ft.com:80/support/kb/articles/Q307/2/55.ASP&NoWe
bContent=1>
(you will need to make this all one line)
which should tell you if your installation is OK.

TTBOMK Date() is a VBA function and is not related to ADO. But if your
references are faulty, then nothing may work.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)