Registering VFPOLEDB to use as linked server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mark J. McGinty (mmcginty_at_spamfromyou.com)
Date: 03/05/04 

Date: Fri, 5 Mar 2004 01:53:43 -0800

Greets,

I have a project that accesses heterogeneous data sources. After finding
limitations of the applicable ODBC driver, I found the latest OLE DB
provider for Visual FoxPro on MSDN. It works well if I connect directly to
VFP, however, I can't use VFPOLEDB.1 as the provider in a linked server.

After I installed VFPOLEDB it didn't even show up as an option when defining
a linked server. A little registry exploration showed me that the component
was registered under the current user, not the local machine. I then
re-registered the component by calling REGSVR32, which did cause it to
appear as an option, but it still does not work.

---------------------------
SQL Server Enterprise Manager
---------------------------
Error 7403: Could not locate registry entry for OLE DB provider 'VFPOLEDB'.
OLE DB error trace [Non-interface error: Provider not registered.].
---------------------------
OK
---------------------------

I set permissions for the vfpoledb.dll file to Everyone->Full to rule-out
security -- that ain't it (at least not at the NTFS level.)

I was able to use the OLE DB Provider for ODBC, with the "Microsoft Visual
FoxPro Driver" to create a linked server, tables and views are listed in EM,
but cannot use a 4=part name to query the data, apparently because that
driver doesn't understand the owner-qualifier segment of the name.

Also, using ODBC, though sp_tables_ex returns a correct list of tables,
sp_columns_ex returns an empty rowset, and
ADODB.Connection.OpenSchema(adSchemaColumns) returns an equally disparaging
error. (A connection opened on VFPOLEDB fully supports OpenSchema, so this
part is mostly a non-issue.)

So, if anyone has carnal knowledge of this stuff, your input will be
appreciated.

-Mark

Relevant Pages

  • Re: Reading mm datasource
    ... I tried opening Word in it's own window and setting the datasource ... I have been told that when XP SP2 was released, an odbc driver was not able ... Word is trying to connect using the OLE DB provider ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Reading mm datasource
    ... I've had a look around and seen some of the comments about XP SP2 and ODBC but simply haven't been using that combination myself except for testing stuff from other people. ... since it appears from your research that it may be an issue to do with simultaneous use of the driver by more than one program. ... I tried opening Word in it's own window and setting the datasource ... Word is trying to connect using the OLE DB provider ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Reading mm datasource
    ... the OLE syntax is not relevant here. ... Doug's post helped me identify that the client has the odbc dbase driver ... Word is trying to connect using the OLE DB provider ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Reading mm datasource
    ... If you don't specify one, it will probably try OLE DB first, then possibly ODBC. ... Doug's post helped me identify that the client has the odbc dbase driver ... Word is trying to connect using the OLE DB provider ...
    (microsoft.public.word.mailmerge.fields)
  • Problem with Linked Server from SQL to DB2
    ... I'm trying to setup a linked server from SQL to DB2 UDB. ... Microsoft provided OLE DB driver for DB2 and the IBM DB2 OLE DB ... -- Invalid schema or catalog specified for provider 'IBMDADB2'. ...
    (microsoft.public.data.oledb)