>Hmmm . . . sounds like a network issue, but don't know what it could be. never encountered this before. If all else fails, might put the DELETE/TABLEUPDATE() in some sort of loop so you could update fewer records at a time. Not the way you would want to do it but . . . :-). you might sandwich it all in a TRANSACTION so you could ROLLBACK if it fails along the way. BTW, I may be wrong about this, but my understanding is that a ROLLBACK cancels ALL changes made during a TRANSACTION, so a TABLEREVERT() should not be necessary after a ROLLBACK. Hope you solve the problem.

Bill,

I guess I will try breaking the process up into smaller chunks. I need some way to make sure that if any one chunk fails that no chunks go through!

I was using the TABLEREVERT to undo the buffered changes that were made outside the transaction (replaces, inserts and deletes).

Does anyone have any experience with the record locking that is done by a network (Novell)?

Thanks,
Shane