Jason,

just replying for Sandeep.

The cpu, mem, disk, handles etc are normal, else we would know that we
stuffed up a query. Access to the same database is allowed by api
calls , local tcpip and remote tcpip.

We have been tracing / logging it and refining where it happens. We
have got as far as this code.


if IndexDefs.Count = 0
then IndexDefs.Update;


The code that contains this segment works for 12 different tiny tables
once an hour most of the time. If I have six copies of this running on
6 different gdbs. one might fail every two days on my PC. The customer
however sees it 6 times a day.

We are running Madexcept on this as well and will let you know what we find.


IB Objects wrote:

> > But it works sometimes before freezing. There is no pattern to it. The
> > table is a small one with about 200 records.
>
> What is the CPU usage of the frozen process?
> How about disk activity?
> How about virtual memory usage?
>
> Can you pinpoint where in your code this is happening? (Do a log file if
> necessary please.)
>
> Jason Wharton
> www.ibobjects.com