Thanks, I have a catch 22 here. The ODBC driver returns a value out of range error whenever I do a select on a field that is a float. The ADO driver handles floating point fine, but does not like the SUCCESS_WITH_INFO messages that come back with a SELECT that produces no rows. I may have to do a ODBC select without float columns to make sure I am going to get a hit, then do an ADO select on the complete field list.
Peter >> >> >> Peter Hircock wrote: >> >> > I am having a problem when the query returns no rows, if >> I get data all >> > looks good. When I run $sth->execute() on a SELECT that returns no >> > rows, the OLE->ODBC driver is returning a 01001 Information >> Code, with the >> > result. It looks like the ADE driver then enters a long >> loop 65531. >> > Memory ( > 300 Meg ) && CPU ( 100% ) while this is happening. >> >> Looks like the SUCCESS_WITH_INFO issue I'm currently working on: >> > > In the mean time, you might try DBD::ODBC and use the ODBC driver > directly. > > Jeff > > >
