Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > SQL SERVER (TECHNET) > cannot get column information from OLE DB providerMSDASQL
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 6th August 02:53
jesse beveridge7vn-rzz
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


I have an interesting problem, I am running a SQL2005 CTP (Sept) server and I
am attempting to make a stored proc call which uses a linked server to
foxpro. The call works from QA (query ****yzer sql2k) but when I run it
through a sql data adapter in visual studio 2003 (C#) I get the error:
cannot get column information from OLE DB provider "MSDASQL" for link server
"***X". I also get an error when I run the same stored proc call through
osql or isql. Is this an MDAC issue, a framework issue? Am I even posting
to the right group?

-- Jesse
  Reply With Quote


  sponsored links


2 6th August 03:40
v-kevy@onlinemicrosoftcom kevin yu
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


Hi Jesse,

I tried it add a linked server to a foxpro database in SQL server 2005, and
then created a stored procedure to get data from foxpro database. When I
use SqlDataAdapter.Fill method to fill a dataset, everything works fine.
Could you let me know what provider are you using to connection to Foxpro
database? I suggest you use Microsoft OLE DB Provider for Visual FoxPro.

8.0 version can be downloaded from

http://www.microsoft.com/downloads/details.aspx?FamilyID=0f43eb58-7a94-4ae1-
a59e-965869cb3bc9&DisplayLang=en

9.0 version can be downloaded from

http://www.microsoft.com/downloads/details.aspx?FamilyID=e1a87d8f-2d58-491f-
a0fa-95a3289c5fd4&DisplayLang=en

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
  Reply With Quote
3 6th August 03:40
jesse beveridge
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


Actually I using the OLE DB for ODBC driver Version 2.81.1117.0
(MSDASQL.dll).

I remember have issues talking older versions of FP OLEDB for fox.

-- Jesse
  Reply With Quote
4 6th August 03:41
jesse beveridge7vn-rzz
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


An interesting note; in osql from a windows XP box (patched/updated/et al)
connecting to the sql2005 sql server, I can run osql (osql sql2000 ver.) and
run the same query the stored proc is using;
select * from OPENQUERY(LINKEDSERVER,'select * from foxprotable')
and it works fine.

But when I run the stored proc I get:

Msg 7350, Level 16, State 2, Server SQLSERVERNAME, Line 1
Cannot get the column information from OLE DB provider "MSDASQL" for linked
server "LINKEDSERVER".
OLE DB provider "MSDASQL" for linked server "LINKEDSERVER" returned message
"[Microsoft][ODBC Visual FoxPro Driver]File 'foxpro.dbf' does not exist.".

-- Jesse
  Reply With Quote
5 6th August 04:22
v-kevy@onlinemicrosoftcom kevin yu
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


Hi Jesse,

I suggest you try to use the latest version of Foxpro OleDb driver to link
to the foxpro database. It might help you to get over the problem.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
  Reply With Quote
6 6th August 05:53
jesse beveridge
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


Unfortunatly I can't use the oledb driver, it's do***entation states:

When used with SQL Server as a "linked server", the Provider
supports query operations only. The Provider does not support update
operations (Update/Insert/Delete).
  Reply With Quote
7 6th August 06:39
v-kevy@onlinemicrosoftcom kevin yu
External User
 
Posts: 1
Default cannot get column information from OLE DB providerMSDASQL


Hi Jesse,

I suggest you try to following this KB article to do a distributed query
with Foxpro to see if it still works with the OleDb provider.

http://support.microsoft.com/default.aspx?scid=kb;en-us;207595

Also, since your application is connecting to a SQL server, have you tried
using a SQL native provider instead?

Beside, you can also post in the SQL server newsgroups, there will be more
professionals who can help you on this issue there.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
  Reply With Quote


  sponsored links


Reply


Thread Tools
Display Modes




Copyright 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666