Dueling references? 1

[diamondsc]

I ran into a perplexing problem. The app front end and back end is in Access 2000. I had the following references in use:

Visual Basic for Applications
Microsoft Access 9.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.7 Library

All works well using the developers package, no worries. I created an workstation installation using InstallShield. Told it to include the MS Access driver and the Access runtime. When I install it on a workstation, the Date() and Mid() functions won't work. I can remove the ADO Library and the code that references it, copy the new .mde file to the workstation, and those functions work fine. Can someone tell me what's going on? Thanks.

P.S. I want to use ADO to occasionally transfer a record from the Access database to a SQL Server database table so I will eventually need the ADO reference.

 

[jazzz]

Your version of ADO is not the same as on the target machine. You can search Microsoft site and locate the corresponding runtime for the version of ADO you used to compile your app and install it on the target.

http://www.microsoft.com/downloads/...f2-cae7-493d-b0f3-ae36c570ade8&DisplayLang=en

Life's a journey enjoy the ride...

jazzz

 

[diamondsc]

Thanks jazzz. Instead of using Microsoft ActiveX Data Objects 2.7 Library I used Microsoft ActiveX Data Objects 2.5 Library and everything worked fine.