There is an article in the M$ knowledge base stating
that the ODBC drivers will only install on a machine
that has one of the M$ products (listed in the error
messga box you get) previously installed.

>I have just run across a problem I thought I'd toss out to this group. > >I have recently completed a large application, that was written using Visual FoxPro 5.0, Visual Basic 5.o, and Visual C++ 5.0. This application is required to process adhoc queris against large tables (700,000 to 1,000,000 records) in real time. I used FoxPro for my data handler, compiled my code as an in process DLL, and distributed the run time module. > >I downloaded the March, 1997 ODBC driver from Microsoft, and verified that the eula gave me distribution rights with my run time application. The project has been installed on numerous test machines, and is performing flawlessly. > >Today my client began installing the application on production machines. The ODBC driver refused to install. A message box popped up indicating that the product required MS Word, MS Access, MS Excel, or FoxPro to be installed before the ODBC driver could install. Evidently each of my clients test machines had one of these installed. > >I have re-read the eula. It specifically states that I CAN distribute the product with my application. > >I've been trying to get in contact with someone from Microsoft all day, unsuccessfully. Has anyone else run into this? If so, how did you resolve the problem. This is particularly sensitive because my client is a defense contractor, and the project is government funded. They are very much aware of software licensing. > >Appreciate any input. > >Best wishes, > >Jim Hart