If that's NOT the case then you should make sure that any $sth really go out of scope or are cleaned up before executing the next call. Maybe consider using the syb_no_child_con option to make sure that DBD::Sybase doesn't attempt to open a second connection if there is already an "active" statement handle on the current $dbh.
Michael
In reply to Re^3: DBD::Sybase::db prepare failed after nth iteration
by mpeppler
in thread DBD::Sybase::db prepare failed after nth iteration
by perlsen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |