Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VFP 3.0 odbc installation error
- Thread starter kraus
- Start date
It's difficult to even speculate on the problems that might be occuring. VFP 3.0 was never tested on ME. I'd suggest you update to VFP 8.0 and then see if you have any problems. At the very least it won't be with ODBC - MS hasn't supplied VFP ODBC drivers since 6.0. VFP 7.0 & 8.0 install the VFP OLEDB provider.
Rick
Rick
- Thread starter
- #3
i know there was a fix for it in the microsoft knowledge database, but now i can't find it.when i ran into this problem before i had to delete some odbc drivers from the control panel (odbc drivers icon). i can't use version eight because my production software was written on 3.0. i've tried to use the upgrade wizards to upgrade my software to 7.0, and there were many problems. i suspect 8.0 would have the same problem. anyway, there is a fix for this - it is easy - i just can't remember it.
kraus (MIS) Apr 29, 2003
setting up VFP 3.0 pro to two windows ME machines.
Is it VFP 3.0b? Maybe the problem is just that: lower version of VFP 3.0
I had similar problem sometimes with customers installing my programs written in VFP 3.0b on Win98 1st edition machines...
Regards,
Ilya
setting up VFP 3.0 pro to two windows ME machines.
Is it VFP 3.0b? Maybe the problem is just that: lower version of VFP 3.0
I had similar problem sometimes with customers installing my programs written in VFP 3.0b on Win98 1st edition machines...
Regards,
Ilya
- Thread starter
- #5
To Kraus:
1. Check what's installed on these ME machines, what other DBM(s) may there be. You might have to uninstall them, run VFP 3.0 installation setup and then install these DBM(s) again. Making sure you are not logged in into the local network during VFP installation may also help.
2. If anything fails - re-run the VFP 3.0 setup and make sure you are NOT installing ODBC drivers. Or uninstall VFP alltogether and start anew, use Custom Setup and uncheckmark all the ODBC drivers in the list of the components to install.
To RGBean:
Rick, FYI: VFP 3.0b works on my ME machine (Pent. III 800 MHz, 128 MB RAM, 100 MHz bus) perfectly since June 2000. And I ran all kinds of weird commands and programs in VFP 3.0 on this box! It's not exactly MS's testing, but VFP 3.0 works on WinME, you can trust me on this one.
Regards,
Ilya
1. Check what's installed on these ME machines, what other DBM(s) may there be. You might have to uninstall them, run VFP 3.0 installation setup and then install these DBM(s) again. Making sure you are not logged in into the local network during VFP installation may also help.
2. If anything fails - re-run the VFP 3.0 setup and make sure you are NOT installing ODBC drivers. Or uninstall VFP alltogether and start anew, use Custom Setup and uncheckmark all the ODBC drivers in the list of the components to install.
To RGBean:
Rick, FYI: VFP 3.0b works on my ME machine (Pent. III 800 MHz, 128 MB RAM, 100 MHz bus) perfectly since June 2000. And I ran all kinds of weird commands and programs in VFP 3.0 on this box! It's not exactly MS's testing, but VFP 3.0 works on WinME, you can trust me on this one.
Regards,
Ilya
- Status