Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Openquery
Message
From
29/02/2004 15:35:05
Guy Pardoe
Pardoe Development Corporation
Peterborough, New Hampshire, United States
 
General information
Forum:
Microsoft SQL Server
Category:
SQL syntax
Title:
Miscellaneous
Thread ID:
00881389
Message ID:
00881903
Views:
37
That makes sense... but I'm getting errors trying this.


So I figured... let me see what happens when I create a linked server to a DBC. I used the example you provided below and I get the same kind of connection error.

I have VFP8.0 on an XP Pro machine with SQL Server 2000 developer edition installed.

The only thing I can see different in the provider string are my paths and DBC name, and the fact that I'm refering to "C:\Whatever\mydatabase.dbc" instead of the UNC naming convention you used in your example.

Does it have to be UNC naming convention?

Guy




>It'll be almost the same, but SourceType=DBF and SourceDB should be the directory with free table(s).
SourceType=DBF; SourceDB=h:\Temp;
>
>
>>Sergey,
>>
>>How would I connect to Fox 2.x tables? What would the provider string be?
>>
>>Guy
>>
>>
>>
>>>>The table is part of a database. I know the second syntax you give and using that syntax I get a result but that doesn't solve my original problem (combine 2 sql tables and 1 VFP table on a linked server)
>>>
>>>Hi Hans,
>>>
>>>We've two issues here:
>>>
>>>1. Four part name for a VFP table in DBC
>>>I just tested and it works for me. The linked server is setup with Provider string only
DRIVER={Microsoft Visual FoxPro Driver};
>>>Exclusive=No;Collate=Machine;Deleted=Yes;Null=No;
>>>SourceDB=\\Target_1\vol_1\daily\lccqueue\testdbc.dbc;SourceType=DBC;
I would suggest that you play more with it and try to figure out why it doesn't work for you.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform