It always helps to have documentation to fix these problems :)
I solved the problem using
$dbh->{LongReadLen}= 10000;#Memory hog if not careful, read DBI doc!
$dbh->{LongTruncOk}=1;
Thank you for your help.
CW2 Daniel Maldonado
Programmer Analyst USPFO-CT
860.524.4931 DSN: 636-7931
-----Original Message-----
From: Maldonado, Daniel CW2 CTARNG
Sent: Friday, August 15, 2003 12:39 PM
To: 'Tim Bunce'
Cc: '
Subject: RE: FW: Update query breaks future select! (Continued!!!)
Finally found the error message.
Now to the internet to try to find a solution but I send you this just in
case
you have a quick fix for me :)
!! ERROR: 1 '[Microsoft][ODBC Microsoft Access Driver]String data, right
truncated on column number 1 (itdesc) (SQL-01004)(DBD: st_fetch/SQLFetch
(long truncated) err=1)'
<- fetchrow_array= undef row17 at testdb.pl line 27
DBD::ODBC::st fetchrow_array failed: [Microsoft][ODBC Microsoft Access
Driver]String data, right truncated on column number 1 (itdesc)
(SQL-01004)(DBD: st_fetch/SQLFetch (long truncated) err=1) at
C:\common\pgming\perl\testdb.pl line 27.
CW2 Daniel Maldonado
Programmer Analyst USPFO-CT
860.524.4931 DSN: 636-7931
-----Original Message-----
From: Tim Bunce [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 6:43 PM
To: Maldonado, Daniel CW2 CTARNG
Cc: [EMAIL PROTECTED]
Subject: Re: FW: Update query breaks future select! (Continued!!!)
On Tue, Aug 05, 2003 at 01:18:49PM -0400, Maldonado, Daniel CW2 CTARNG
wrote:
> Why would the statement:
>
> my $newHashRef = $rs->fetchrow_hashref();
>
> not return any records from an access DB when
> the field contains the following characters:
>
> </TD></TR><TR><TD BGCOLOR=#FFFFFF COLSPAN=2><FONT SIZE=+1><B>Added By
> Seller</B></FONT></TD></TR><TR><TD BGCOLOR=#FFFFFF COLSPAN=2>
>
> I am starting to believe that it may have something to do with the hash
> table.
> The field is a memo field if that helps anyone.
>
> Can't seem to figure this one out and it is kicking my ?%$#.
>
> Wish I could see the value returned when this fails but of course I can
not
> :-)
What does the DBI trace show?
Tim.
