Jim Starkey wrote:

> How about:
>
> CREATE TASK <name> PROCEDURE <procname> SCHEDULE <schedule>
>
> The only can want to handle security is for the task to run as the
> account that scheduled it. Leave everything else to the task. I
> suggest you pass the task its name, however.

KISS at it's best. Something I like about Firebird anyway.

> This an excellent start. I agree with your functionality, but disagree
> on the division of work between the scheduler and the task handler. I'd
> rather see the scheduler schedule tasks, period, leaving task semantics
> strictly up to the task/procedure. I also think you have to make a
> case for non-times tasks.

If you want to schedule start and stop dates - you set up a procedure
that checks your own table of tasks and switches them on and off as
required. You can then schedule when those updates are checked.

There is no need to create an all singing all dancing bloated function,
just a "do this now" will fill most requirements?

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
Treasurer - Firebird Foundation Inc.