>
>
> On Tue, Oct 22, 2002 at 09:54:03AM -0400, Jeff Urlwin wrote:
> >
> [SQLFetch()]
> > The first time through, we see (snipped from trace below)
> >
> > > fetch col#4 SC_VALUE datalen=0 displ=256
> > > fetch col#4 SC_VALUE datalen=19 displ=256
> >
> > The second time through, I see:
> > > fetch col#4 SC_VALUE datalen=19 displ=256
> > > fetch col#4 SC_VALUE datalen=19 displ=256
> >
> > I *think* that's a driver problem. You indicated it works in another
> > environment (query analyzer). Is that using the ODBC driver
> too? How about
>
> incomplete sentence? How about...?
Sorry -- brain problem, this morning. I was going to say, how about MS
Query (not analyzer, but the query that comes with MS office which just
queries the db), then I looked further to see you were on Linux....can you
give us a little more about your configuration? I can guess that you may be
using one of the following:
- 1) using DBI, DBD::Proxy or and MS ODBC drivers on the SQL Server side.
- 2) using DBD::ODBC and EasySoft OOB or some other bridge
- 3) using DBD::ODBC and something like FreeTDS
- 4) some other config...????
What version of the MDAC is on your SQLServer itself? Since nearly all of
these are dependant upon the ODBC driver on the server (or wherever the
bridge is installed). If you can update that to MDAC 2.7, that would be
great. There were some issues with 2.6 and below.
Jeff
>
> > What driver/version are you using? What database? I'd like to
> see if I can
> > reproduce here.
>
> This is where my knowledge goes a bit flakey. It works in MS Query
> Analyzer, which, according to someone here, isn't using ODBC.
>
> Query analyser version: 7.00.623
>
> SQL Server version 7.00.961, SP3; on NT 4, SP6
>
> Cheers,
>
> --
> dave thorn | [EMAIL PROTECTED]
>
