>>>.....
>>>>>Reprocess is set to 2 seconds
>>>>
>>>>i'd set it higher -- network traffic can do that...
>>>
>>>But there's AbsolutelyPositivelyCatagoricallyNOTHINGWrong with the network! (Quote from Network guy)
>>
>>i'll take his word for it, but i don't see anything else. i'm sure you have the records locked for as short a time as is possible... when we hit that, we blame the network. of course, ours don't sit in that loop unless one of the machines freezes with a record locked...

I sometimes SET REPROCESS to loop indefenitly (with the option to abort it with ESCAPE)
is some cases this is acceptable (and works)

Arnon