Re: Linked Server and OLEDB Problem
- From: "Bill Bach" <goldstar@xxxxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 16:20:20 -0600
datenisis wrote:
> Hi Bill,
>
> I tried this and it works for other tables
>
> ie select * from DEMODATA.DEMODATA..BILLING
>
> but when I do "select * from DEMODATA.DEMODATA..X$FILE" I get the
> following:
>
> OLE DB provider 'MSDASQL' returned an unexpected data length for the
> fixed-length
> column '[DEMODATA].[DEMODATA]..[X$FILE].Xf$Reserved'. The expected
> data length is 10, while the returned data length is 0.
>
> Is this possible to fix?
>
> Thanks,
>
> -d
The Xf$Reserved field is simply reserved space. Since it is
uninitialized, it might be giving fits to the SQLServer driver if
"unexpected" data gets returned for it. If you're having problems
getting that data into SQLServer, just skip it! Try this instead:
SELECT Xf$Id, XF$Name, XF$Loc FROM X$File
If this works, then you'll just need to avoid this one field.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Sydney: Pervasive.SQL Service & Support Class - 02/27/06 ***
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***
.
- References:
- Linked Server and OLEDB Problem
- From: datenisis
- Re: Linked Server and OLEDB Problem
- From: Bill Bach
- Re: Linked Server and OLEDB Problem
- From: datenisis
- Linked Server and OLEDB Problem
- Prev by Date: Re: Communication Threads
- Next by Date: Re: Pervasive 2000i data recovery question
- Previous by thread: Re: Linked Server and OLEDB Problem
- Next by thread: Passing Btrieve OwnerName to Crystal Reports
- Index(es):