Errors in connecting Visual Fox Pro as linked server in 2005 - HEL

I can set up a linked server to a FoxPro DB in SQL 2000 but it fails when
trying to set up the linked server in 2005. I know the MS site says somethin
g
about leaking memory with the linked server but I don't even get a link that
works.
Here is what happens in a Win2003Server, SQLServer2005, latest VFPOLEDB from
MS site environment.
1) If I try to create a linked server from the management studio, it says:
'(null)' is an invalid product name. (Microsoft SQL Server, Error: 15429).
There are only three fields to fill out and product name is not required whe
n
I try to make the linked server in 2000.
2) If I use a SQL command to create the linked server, I can make it without
the product name but it does not work in 2005 but does in 2000.
sp_addlinkedserver 'SERVER1', '', 'VFPOLEDB', 'c:\company.dbc'
Looking for thoughts on how to troubleshoot this!!
Doug HoogervorstThink I am closer now. It turns out that MDAC 2.8 SP2 for Windows Server 200
3
is not showing VFPOLEDB as a component when I run the component checker. I
have tried regsvr32 to register the dll but no luck. Thoughts on how to get
MDAC to recognize this OLE DB provider?
"djh" wrote:

> I can set up a linked server to a FoxPro DB in SQL 2000 but it fails when
> trying to set up the linked server in 2005. I know the MS site says someth
ing
> about leaking memory with the linked server but I don't even get a link th
at
> works.
> Here is what happens in a Win2003Server, SQLServer2005, latest VFPOLEDB fr
om
> MS site environment.
> 1) If I try to create a linked server from the management studio, it says:
> '(null)' is an invalid product name. (Microsoft SQL Server, Error: 15429).
> There are only three fields to fill out and product name is not required w
hen
> I try to make the linked server in 2000.
> 2) If I use a SQL command to create the linked server, I can make it witho
ut
> the product name but it does not work in 2005 but does in 2000.
> sp_addlinkedserver 'SERVER1', '', 'VFPOLEDB', 'c:\company.dbc'
> Looking for thoughts on how to troubleshoot this!!
> Doug Hoogervorst|||Hi Doug,
As you know, the FoxPro and Visual FoxPro OLE DB data provider is not
installed with MDAC. For the record, it's downloadable from
msdn.microsoft.com/downloads/updates. If you already have it you might want
to verify that you've got the latest version.
Here's what works for me in SQL 2005 using the Linked Server dialog:
Providers list: VFPOLEDB shows as an entry
Linked Servers > New Linked Server ...
Linked Server: MyLinkedServer
Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
Product name: Visual FoxPro (I think this is optional)
Data source: "C:\Program Files\Microsoft Visual
FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
spaces in the string.)
Provider string: VFPOLEDB.1
Location: (blank)
Catalog: (blank)
Security page and Server Options page take defaults.
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"djh" <djh@.discussions.microsoft.com> wrote in message
news:F93EBC44-2A78-4801-8DB0-C35F13CE876B@.microsoft.com...[vbcol=seagreen]
> Think I am closer now. It turns out that MDAC 2.8 SP2 for Windows Server
> 2003
> is not showing VFPOLEDB as a component when I run the component checker. I
> have tried regsvr32 to register the dll but no luck. Thoughts on how to
> get
> MDAC to recognize this OLE DB provider?
>
> "djh" wrote:
>