Raul,

> Let me know if you get to the bottom of why you're seeing different
> results on different machines.

I opened a support ticket, but we didn't find a solution yet. Since the
reason of my support request was just to make sure, that I can rely on
the execution of my jobs, I didn't investigate that further.

Here some snippets by Tim:

<<
I've double-checked the EDB source code, and the
only place where EDB sets Enabled:=False for jobs is in the
functionality for disabling a job or jobs, and it is definitely
initializing all jobs as enabled during startup.
>>

<<<< the issue occurs also on another computer - it's also a remote
server with OS 2008 Server R2, see attached screenshot.  >>>>

<<
Hmmm, this is really weird.  Did you check to see if you're executing
this statement at any time:

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=DISABLE_JOBS
>>

Uli

So why not just create a table "JobsRunning" in a global database and have the job add a row in the JobsRunning table with the job name and start time. When the job completes, the job deletes the row.  Put this within an exception block so the Finally statement always executes to delete the row when the job completes. The global database could have a stored procedure to do this for you. Nice and simple. Another function could accept the job name and return the time it has been running, or -1 if it is not running.

Simple. Yes?

Barry