>>I will sooner. But what I have explained so far is the immediate solutions we made to for us to go on with the projects as changing the SET REPROCESS may require major changes on our error handling code. Thanks for your patience.
>
>Jess,
>
>Let me see if I understand this. You have a system that has a set of updates that must be made as an all or none operation. You had a problem and removed the transaction so that there is no longer a guarantee that all updates or no updates occur and there is a possibility of data corruption and inconsistency. You have become aware of how to fix this problem. You have decided not to fix it because it would require you to test the code again. Is this what you are saying?

We will ofcourse but not too soon because we have to see what specific modules are in need of the said fixes. If it is too soon we might aggravate the situation because up to now, none of the clients are complaining so far but at least we are already aware of the situation and doing something.