Re: :ODBC bug?

[Roger Perttu]

Dave Thorn wrote:

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...?

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.

According to me :-) newer versions (7+) of Query Analyzer use ODBC, older versions might use DB Library
You might try osql (O for ODBC) from the command prompt.

Query analyser version: 7.00.623

SQL Server version 7.00.961, SP3; on NT 4, SP6

try: ppm query DBD-ODBC

This is what I get:
E:\Programs\Perl>ppm query DBD-ODBC
DBD-ODBC [0.45_18] ODBC driver for the DBI module.

Can you try to run your code on a different machine where it's possible to try 0.45_18?