server to VFPOLEDB working in 2000 but not in 2005?

I have run the following command and opened a working linked server in SQL Server 2000 but it fails for 2005.

sp_addlinkedserver 'AZ','','VFPOLEDB','c:\comp01\company.dbc'

To test, I run: select * from openquery(AZ, 'select * from contact') and I ge

Msg 7399, Level 16, State 1, Line 2

The OLE DB provider "VFPOLEDB" for linked server "AZ" reported an error. Access denied.

Msg 7350, Level 16, State 2, Line 2

Cannot get the column information from OLE DB provider "VFPOLEDB" for linked server "AZ".

The specs on the working machine: WinXP Pro, SQL Server 2000 Developer's Edition, SP4, latest VFPOLEDB from MS site.

The specs on the non-working machine: Windows Server 2003 (std), SQL Server 2005 Developer Edition SP4, latest VFPOLEDB from MS site.

Other things I have done and/or noticed:

- in the install notes, it says something about security through component services, MSDTC, having to check everything. Did that.

- if I don't use a SQL command from query analyzer and try to add the linked server by right clicking on Server Objects\Linked Servers, it demands a Product Name. Null (and ' ') is not a valid entry.

Looking for help on this.

Doug

Think I'm closer. Turns out that MDAC has not recognized VFPOLEDB despite having downloading and installed it on Windows Server 2003. I have now tried regsvr32 and it says it's registered but still not listed in MDAC (used the component checker). Thoughts?
|||Sorry, I don't have any suggestions for you. I just thought I'd sympathize because I am running into the same problem with MSDAORA instead of VFPOLEDB. I'd be interested to hear what progress you end up making.