Re: VFPOLEDB as a link server in SQL Server 2000

Hi Cindy,

In SQL 2K EM, there are five fields to complete to create a linked server:
The linked server name, the provider that is installed on the server (chosen
from a dropdown list of installed providers), the "product name", the "data
source", and the "provider string". The linked server name, not the product
name, is what shows up under linked servers in the Security tab. If the
installed provider is already filled in, what then is the significance of the
"product name"? If the data source is the path to the DBC, what is the
significance of the "provider string"? Haven't I already designated that in
the provider name dropdown?

Clarification?
--
Phil Hegedusich
Senior P/A
IIMAK
----
A skeleton walks into a bar and says, "I need a beer and a mop."


"Cindy Winegarden" wrote:

> 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. .....
>
>
>
.

Relevant Pages

  • Re: Linked server to as400 - for the love of god please help.
    ... > There is an ODBC DSN on the server machine. ... Creating a linked server using ... > OLE DB provider 'MSDASQL' reported an error. ... > So i instead create a linked server using IBM's own OLEDB provider. ...
    (microsoft.public.sqlserver.server)
  • Re: OPENDATASOURCE problem
    ... >tbl_CLASSES is an SQL Server table. ... >Microsoft OLE DB Provider for SQL Server error '80040e14' ... >Ad hoc access to OLE DB provider 'Microsoft.Jet.OLEDB.4.0' has been denied. ... >You must access this provider through a linked server. ...
    (microsoft.public.sqlserver.programming)
  • Re: Linked server from SQL Server to Access db on network share?
    ... What it looks like is this: SQL can create a linked server to a file on a remote share, but you can't query against it using Query Analyzer from any system other than the one hosting SQL... ... EXEC sp_tables_ex 'OLDSQL' ... OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. ...
    (microsoft.public.sqlserver.msde)
  • Re: Errors in connecting Visual Fox Pro as linked server in 2005 - HEL
    ... Here's what works for me in SQL 2005 using the Linked Server dialog: ... Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro ... It turns out that MDAC 2.8 SP2 for Windows Server ...
    (microsoft.public.sqlserver.connect)
  • Re: Determining Fully Qualified Name for Linked Servers
    ... provider and the ODBC driver to support the same functions. ... >If I run it for the Linked Server configured with the Foxpro driver I ... >Catalog: NULL ... >Invalid schema or catalog specified for provider 'MSDASQL'. ...
    (microsoft.public.sqlserver.connect)