I'm telling you, it's a locking problem. It only takes one sick git to grab the page, and leave it that way by doing nothing else, and the rest of us are fcuk'd. I've experienced this basic error so many times when testing software. If a sick git does this, the only way around it is to kill (not literally, but you'd like to

) that user.
It was actually the way new programmers were taught, not realising that there might be more than one user trying to access the program at the same time. The solution is not to lock the document, but to allow a slight delay at the point you press the final send. That way, the record doesn't get locked, and the chances of multiple persons hitting the tit at exactly the same time are remote.
How many times when working within an application have you seen the message, 'this may take a few minutes', but it rarely does. These people have worked it out. The 'few minutes' are when a lot of people hit the tit at the same time, and it's clearing them one by one.