Re: VFPOLEDB as a link server in SQL Server 2000
- From: "Cindy Winegarden" <cindy_winegarden@xxxxxxx>
- Date: Mon, 6 Jun 2005 19:17:29 -0400
Hi Phil,
Product name: MyLinkedServer. This creates a linked server named
MyLinkedServer and MyLinkedServer will show in the Linked Servers branch of
the tree in EM.
Data source: Mine is "C:\My Documents\Visual FoxPro Projects\Test.dbc"
including the quotes. (I suppose if your path doesn't have spaces the quotes
won't be required.) If you aren't connecting to a DBC (using only a free
table directory) then just use the directory name.
Provider string: VFPOLEDB . This is the name of the provider you're using.
It's interesting to note that in SQL 2005 the available providers are listed
and it then becomes more apparent that this is a string containing the name
of the provider.
Location and Catalog are grayed out.
--
Cindy Winegarden MCSD, Microsoft Visual Foxpro MVP
cindy_winegarden@xxxxxxx www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
"Phil H" <philhege@xxxxxxxxxxxxxxxxx> wrote in message
news:9C1F8C77-5630-4EA3-85BD-0D37160C41CD@xxxxxxxxxxxxxxxx
>I can't seem to find any examples or coherent explanation of the correct
> elements to put in the Enterprise Manager interface in order to create a
> pure
> OLEDB connection to a FoxPro DBC. .....
.
- Follow-Ups:
- Re: VFPOLEDB as a link server in SQL Server 2000
- From: Phil H
- Re: VFPOLEDB as a link server in SQL Server 2000
- References:
- VFPOLEDB as a link server in SQL Server 2000
- From: Phil H
- VFPOLEDB as a link server in SQL Server 2000
- Prev by Date: recordset using ADO 2.8 and a Dataset using ADO.net
- Next by Date: Re: Linked Server in SQL Server 2000 Evaluation Version
- Previous by thread: VFPOLEDB as a link server in SQL Server 2000
- Next by thread: Re: VFPOLEDB as a link server in SQL Server 2000
- Index(es):
Loading