>Nadya,
>
>>So, I have something like this
>>ON ESCAPE plStop = messagebox('Are you sure you want to stop replace process?,36,'Stop process')=6
>>
>>So, user can hit ESC and the process would be stopped.
>
>I really wonder about allowing this. I think you have a huge potential to really hose your database by allowing partial commit of a table wide change. If the replace has finished half way through the process when it's interrupted, are the changed records still valid? are the still unchanged records valid?
>
>Then you mention that other replaces are also involved, what if 2.5 out of 4 replaces complete?

In my opinion, user should be able to always stop any process, he/she started. In this particular case it's not that critical anyway, because users don't work with the main database. Each user works with his/her own workfile. Only after all processes are done and file passed the Final Review, we invoke Update Engine to update the main database...

However, you might be right. If process was interrupted, may be we want to undo the changes, which were already done, and do it automatically (or ask the user).

I'll discuss this problem with my manager and my colleagues, we may want to change the logic a little bit.

I still think, that we should always give a user a flexibility of easy ESCAPE. :)