Windows Forum

Ask something
Discussion Locked

ODBC and Foxpro Driver 3.50.3428.00

0 helpful
9 replies

by afi

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are having problems installing Foxpro driver version 3.50.3428.00 (using the Microsoft data access pack 97)on any machine(NT server SP4) which has any FoxPro driver version 4,5, & 6 already installed on it.
I have tried renaming the version 6 VFPODBC.DLL driver and replacing
this with the earlier version (3.50.3428.00)but this did nothing.
I have also extracted the dll's from the cab file and copying the ones that relate to the version 3.50.3428.00 into the system 32 file. Then modified the registry to include the driver.When I go to add the driver in the system DSN I get the following error message ' The setup routine for the Microsoft Foxpro Driver could not be found.Please reinstall the driver' . Clicking on OK brings up ' Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed. Component not found in registry.'
I've tried reinstalling the driver again but with no luck. I've also run regserver.
If anyone can help I'd be most grateful

9 replies

by bdivine

I have worked quite a bit with ODBC, but I am unfamilar with the 3.50... version driver. Is it a 16 bit driver? I have a strong inkling that it is. If you are trying to build File and system DSN's you should be using the ODBC configurator in Control panel not the 32 bit one. I addition 16 bit apps look at system rather than system 32. The VFP...DLL you renamed is for Visual Foxpro.

Question why are you trying to back level your ODBC, is it because of a legacy app? Feel free to email your responses to me. BDIVINE@BCBSMT.COM

by afi

The reason we are trying to back level our ODBC is because of a legacy app.
The 3.50.3428.00 driver is a 16 bit driver and I have tried to copy the files over to the system folder but not had much luck there.

by gutridgesj

you can't just rename dll's with ODBC. i would try reinstalling the odbc driver after i deleted all references to that driver. in all the renaming of files and registry stuff going on, there is probably some remnant of the problem. until that is gone, i doubt it will work.

the easiest and quickest solution might be to just wipe the drive clean and re-install the o/s, programs, and then the odbc driver to start afresh.

This discussion is closed to new replies.