Still trouble with ODBC application

[ouuch@xxxxxxxxxxx]

Hello,

well, I'm still fighting with this ODBC application. Thanks for the manual 
tips, so far.

I've now pinned it down to the following behaviour:

Throughout the whole day, single records are retrieved and updated - basically 
this means
writing two stati (start process, end process).

In addition, every 2 minutes a series of select count(*) is run:

        select count(*) from vrosif
        select count(*) from vrosif where sistat='40'
        select count(*) from vrosif where sistat='41'
        select count(*) from vrosif where sistat='43'
        select count(*) from vrosif where sistat='45'

I have PowerLock security auditing installed and this gives me a report of all 
ODBC sql
statements received by the AS/400.

This report shows me that the AS/400 does only some of the select count(*) 
commands and
then the connection is restarted - I have no idea what is causing this?
It could be a bug in the application, the ODBC driver or the AS/400 returning 
something
unexpected?

The main problem is, this is a production system and very important for our 
daily operations.
So I can't play around with this Win2K PC too much.

I've tried the ODBC trace utility of Client Access - but this is just a stupid 
joke. Half an hour
of trace gives about 4 meg of text file with absolutely no timestamp! And the 
trace seriously
slows down the ODBC connection.

So, my main questions are:

-  Anybody know a decent ODBC trace utility for a Win2K pc?
-  I can do a communication trace of the problem, but have no idea how to read 
it. Would
anybody on the list care to take a look? I'd just want to know who breaks off 
the
connection?

thanx,

Oliver