Raul wrote:

DBISAM i believe uses OS for low level locking so there might be a limit
you're hitting - i'd definitely try to get to the bottom of the
query/operation that is being run and see what's going on (how big is
the resultset etc).

Note that last entry about this in newsgroups was some 5 years back so
this is pure speculation in my part and might be something completely
different.

If you do need a faster response you should consider contacting support
direct - i recall Tim had a special debug version of dbsrvr so that
might help pinpoint issue even faster (since you're still seeing these
events on a daily basis).


Raul:

The queries that are being issued actually have single-record result sets; they are live queries intended for editing. Frankly, I'm not even sure the error message I'm getting in the server log indicates an anomaly, it might just be normal record contention. However, my code is designed to trap these and display a dialog asking the user if she wants to retry, and that apparently doesn't fire. Also, they are getting the "cannot establish a connection..." message. Could be either hardware or software (logic) related, don't know, I just need to keep probing.

I agree with you about contacting Tim directly, it had crossed my mind before I even posted. However, I wanted to ask all you good folks for your opinions/ideas; if those didn't help me track this down then Tim was my next step.

Thanks again to you (and Roy) for responding, you gave me a lot to think about.


Norman