Posted by mkarbarz@gmail.com on 02/06/07 23:24

On Feb 6, 6:07 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> mkarb...@gmail.com (mkarb...@gmail.com) writes:
> > I started playing around with the linked server and I got it to the
> > point where I can see the tables from UniData, but when I try to query
> > it using LINKEDSERVERNAME...TABLE I get 'Invalid schema or catalog
> > specified for provider 'MSDASQL'." error. When I try to specify
> > schema using LINKEDSERVERNAME.SCHEMA.TABLE I get 'Invalid object name
> > LINKEDSERVERNAME.SCHEMA.TABLE'; do you know why these errors occur
> > and how to get around them?
>
> To refer to an object on a remote server, you must use four-part
> notation: server.catalog.schema.table. So that's why
> INKEDSERVERNAME.SCHEMA.TABLE does not work.
>
> Unfortunately, I have no idea what will work, since I've never heard of
> Unidata before.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

I started using the 4 part query and I guess I got a step further;
now I'm getting a different error:

the query is: SELECT * FROM AVLIVE..ii.SODET_NF

the error:
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: [Ardent][UniData ODBC
Driver]Invalid column number.]
OLE DB error trace [OLE/DB Provider 'MSDASQL'
IDBSchemaRowset::GetRowset returned 0x80004005: ].
Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.

Any idea what this error means?

[Back to original message]