SQL Toolkit - can't initialize ODBC data source - HELP!

[KHolland]

Here's the deal. I've written a program that connects to an Access 97 database and retrieves information. The Access 97 file is user ID and password protected. This prorgam works perfectly on my machine and on other machines that have CVI and the SQL toolkit installed.

When I create a distribution kit and install the software on a "foreign" PC the software cannot connect to the database. Is there a library file or something that I'm not including that would cause this to happen?

I've also got an error window that should pop up in the event that an error occurs during any ODBC command (including connection). This window does not come up because the DBErrorMessage command returns nothing. So naturally, it
doesn't show the message popup because I'm then sending it a NULL string.

What's going on??? Please help.

[KHolland]

I have found the answer to my own question. Embedded within a readme.txt file (which are usually pointless in nature) I found some very interesting information. A list of "quirks" and workarounds for almost all the database formats (including Access 97). Also I found the list of files that needed to be included within the software package in order to allow CVI programs to correctly reference ODBC data sources.

If anyone else ever has this proble... take a look in the readme.txt