I found the problem. The VFPOLEDB.EXE installer screws up when it installs on Win2003 Server and does not set registry entries correctly. Here's the fix:
From:
http://www.dbmonster.com/Uwe/Forum.aspx/foxpro/4802/HowTo-Configure-VFPOLEDB-on-W2K3Hi Owen:
If you have installed the OLE DB Provider as Cindy suggested, you might be
seeing a problem with the installation software where it does not register
the provider for all users. Here is a suggested workaround:
1. Make copy of C:\Program Files\Common Files\System\Ole DB\vfpoledb.dll*
2. Go to Add/Remove programs, and uninstall Microsoft OLE DB Provider for
Visual
FoxPro
3. Move copy of vfpoledb.dll back to C:\Program Files\Common
Files\System\Ole DB\,
and make sure the filename is vfpoledb.dll.
4. Start/Run this:
regsvr32 "C:\Program Files\Common Files\System\Ole DB\vfpoledb.dll"
* The disadvantage of this approach is it will also remove the C:\Program
Files\Microsoft Visual FoxPro OLE DB Provider\ folder. This folder contains
a Doc folder holding the helpfile dv_FoxProvider.chm and optionally a
sample Northwind
database in the Samples folder. If you wish to retain these, you would need
to make a copy of the C:\Program Files\Microsoft Visual FoxPro OLE DB
Provider\ folder before step 2 above.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
