>>This person in my app, is a serious candidate to be kicked off by an inactivity timer! Next time he won't do that :-)
>
>Pablo,
>
>but we do need to be careful about this stuff. Many of things our users do is a result of how we wrote the app. If my app does not use transactions that way, it only begins, does the update and ends, then I don't care if the user goes for coffee dru==uring the fomr because there is no transaction in process then.

I'm agree with this, this doesn't deals only with transactions, also with file/record locking, sometimes I need to do manteinance tasks that needs the tables openened exclusively (I use some in lunch time and others by the night), and I'm bored of seeing the tasks wouldn't complete cause any has left his app opened! So, for this case I use a timer that drops the user if he in 15 mins, hasn't pressed any key. After the implementation of this, I received some oppinions:

1. The boss was happy seeing tasks completed and told me: good job!
2. the users got annoyed in the first days, but after that they prevent this situation, cause they will lose his changes.

This implementation, in this case, was succesfull for me.

>I enjoy telling stupid user stories as much as the next developer, but I also believe that when a user screws up my application, it is my fault because I allowed it to get screwed up or I didn't give the user good enough feedback to allow them to know what was going on and how it was progressing.

For sure, you are right.