>Hilmar,
>
>I will try this approch. As for your last statement, I have somthing to shut down the users also(almost). My app keeps watch on a table entry if it turns to true A timer is enabled to kill the app in 60 seconds. This works great as long as the app is regitered and running on the users desktop. However, if the app crashes somehow and the user dosen't restart the app and log off of it normally there is still an instance of it running on that machine which keeps my tables locked up. I have to look at the server shared files on the network to see who has it locked. Have you had this problem? If so how do you handle it?
I use a Timer that checks for the existence of a special file, "maintenance.tmp".
And no, my program isn't fail-safe either. But I found through experience that it works in most cases.
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)
