What is the best way to make sure a user doesn't cancel a script?

[keybrdcowboy]

Okay guys (and girls maybe) I have one more question left with this script. I wrote a login script that makes the user type a userID in, then it does a series of checks against a database to make sure that they have the training they are required to have that allows them access to the network. Now I need to set the script up so that they are force to play ball. I do not want someone to say "I am too busy to play their game right now" then hit ctrl+alt+del and end the script. What would be the best way to make sure that the script actually completes? The only thing I can think of would be to have the script create a file at the beginning, and then before exiting the script, remove the file. Then on next login it could check to see if that file exists, and if so, then obviously they canceled the script the first time. Then I could pop up a warning box telling them not to do it again, then if they do, it will lock their account. Anyone else have any other ideas? Thanks a lot for all your help.

 

[EBGreen]

I would put the information in the DB instead of creating a file. It would be too easy for them to just delete the file.

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]

 

[keybrdcowboy]

I was thinking I could bury the file in the windows directory somewhere, and also make it a hidden file. I wouldn't think that the average user would know it was there. There would actually only be a couple people out of 12,xxx users who would know that that file would even exist. I wouldn't expect anyone to even cancel the script, but this is kind of a just in case thing.