Peter Hircock wrote: > Steffen Goeldner wrote: >> >> Umm, maybe I need a trace. But I know you are a courageous boy - >> thus try this first, please: >> >> use Win32::OLE(); > > It's still going, I had to run for the weekend. > > Memory grew to 300 Meg for 3 min, > released memory ( on 32 ) used, > Printed > Error cnt: 32767 > Still going 5 minutes later CPUT still at 100% > > I did a simple select that should have returned no results in < sec.
O.k., there's not much I can do. The test script uses plain Win32::OLE (no DBD::ADO involved!). The question is: Who put 32767 errors into ADO's Errors collection? If I remember, you used the OLE DB Provider for ODBC Drivers (MSDASQL) and the Open Access ODBC driver. I cannot reproduce the problem with MSDASQL and another ODBC driver (e.g. MS Access). Thus I would say it's a problem with the Open Access ODBC driver. On the other hand, you say it works with DBD::ODBC - except for another (the floating point) problem. That's confusing. Maybe a trace with DBD::ODBC shows dubious results from ODBC that irritates MSDASQL? Maybe an ODBC trace (-> ODBC Data Source Administrator) explains what's going on? Steffen
