I have a question about locking a critical section in WinCron.NET. I have a script that reads a list of files from a database table that need to be uploaded to a remote server. The script then begins uploading the files, removing each one from the table upon a successful upload.

I want to schedule the script to run every minute, but I am worried about what might go wrong if a new instance starts while the previous one is still working on its list.

Any advice on this issue? Is there a way to have a script check to see if an instance is already running? Or to lock an object across seperate instances?

Thanks,
Scott

So you’re worried that if while the job is running, the timer will fire to start the job again and you will have two instances accessing the same data. Correct?

No worries. Even though the jobs are scheduled at the same time, the jobs are placed into a queue before they are executed. The system then plucks off the next job from the queue and runs it – waiting until it finished before plucking the next job off the queue.

So you’re safe from WinCron .NET reentering and clobbering your work.

That's great news, Luke. One less thing to worry about Thanks.