Damian Diccox

The way that I have found to get around this is to enable the &#@SUPDETF before the call processes any output (in the default logic of the LU for example) and then disable it after the LU (the exit logic works).
Damian

George,
Thanks for the link I think that it may give me a start on where I need to go

Richard,
The transaction handling will all be handled by the task, the use of the trigger is really only to avoid the delays in running the function which would occur with a cron job. As for the errors and diagnostics, I will handle these in the same way I would with any task.
Thanks for the good advise
Damian

Joseph,
Thanks for the response, I'm OK with the actual execution of the function part; whether it’s by task or direct function call (personally I feel tat tasks are a whole lot better). The part that I'm stuck on is the bit where I can call that ‘stuff’ from the trigger or a stored procedure, in fact I don’t even know where to begin with that part.
Damian