And what should be the ideal solution for you? It's obvious that everyone have to wait until the transaction is complete before saving their data, otherwise the data integrity would be at risk.

The only other thing that I can think of is to delay the save and let the user do other stuff in the meantime:
- SET REPROCESS TO 1 and inform the user to try later if it fail
- Use a timer to try the save at given interval
- Simulate a new thread that will try to save until it succeed

These solutions could have a major impact on the existing design however. Of course, you could also look at how you can optimize the current transaction process so that the impact on the other users is reduced.

>I've talked by phone with my former colleague and here is a general problem I'm not sure has a nice solution.
>
>One batch process performs multiple table updates within transaction (the saving process may take up to 2 minutes). Other users are trying to do changes in these tables as well. Usually you have a scrolling message in such situation 'Wait. Attempting to lock...'
>
>Is there any way to solve the problem?