>You could consider to deploy small 'application' that will permannently hold the file open in shared mode; so you would have to wait for easier identifiable event when some client workstation with faulty process bombs.
Say, that's a really neat idea. Until I find the underlying cause, this would very likely also avoid the main problem I have right now: that no user can make reasonable use of the application. 'Cause - I didn't mention that before - the table that is being blocked is the auditing table; and when that one is blocked, all users get error messages when trying to save records.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
