RE: DBD-ODBC-1.13 --FOXPRO fetchrow_array question

------_=_NextPart_001_01C5FF64.C8C5F55A
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please try issuing another fetchrow_array, if the $sth->err is
SQL-01S01, just to see. It could be that you can safely 'ignore' this
error and use it as a warning.

=20

Jeff

=20

=20

________________________________

From: Yongming Xu [mailto:yxu888@gmail.com]=20
Sent: Monday, December 12, 2005 4:41 PM
To: Jeff Urlwin
Subject: Re: DBD-ODBC-1.13 --FOXPRO fetchrow_array question

=20

Jeff,

=20

Here is the error spooled on the screen:

=20

Z:\pl\dnd>perl odbctest.pl
DBD::ODBC::st fetchrow_array failed: [Microsoft][ODBC Visual FoxPro
Driver]Error in row (SQL-01S01)
[Microsoft][ODBC Visual FoxPro Driver]Error: Column 3 (
convertednotional ) (SQL-22003)(DBD: st_fetch/SQLFetch err=3D-1) a=20
t odbctest.pl line 61.

=20

I attached the test perl DBI script and trace level 9 file for your
review. In the test script, I didn't try to issue fatchrow_array after
the fail as I posted in my original question.=20

=20

thanks very much for your help.

=20

yongming=20

=20

On 12/12/05, Jeff Urlwin wrote:=20

I'm guessing not. I see an error and I'm guessing that it detects the
column type is not correct. Can you set DBI->trace to 9 and send me the

output?

Jeff

-----Original Message-----
From: yongming [mailto:yxu888@gmail.com]
Sent: Tuesday, December 06, 2005 9:36 PM
To: jurlwin@bellatlantic.net
Subject: DBD-ODBC-1.13 --FOXPRO fetchrow_array question

Hello Jeff,

I am using the ODBC DBI to access FOXPRO (visual foxpro 6) tables.
Somehow
in one table some numberical fields mix numerical data with string like=20
"***,***,***". The fetchrow_array method will fail on that row and I
won't
be able to fetch the next row with the same select statement. When I
try to
browse the data using WINSQL with the same ODBC driver, I will get the=20
offending row with those fields filled with "error" togather with the
rest
of the result set.

I am just wondering if the DBD-OBDC module can allow me to do the same
thing
as the WINSQL does: still return the offending rows and allow me to=20
fetch
the next row with the same sql statement.

Thank you for your help.

Cheers,

Yongming
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.11/191 - Release Date:
12/2/2005

=20


------_=_NextPart_001_01C5FF64.C8C5F55A--