Re: DBMS_JOB?

Gary G <ggorbon1_at_swarthmore.edu> wrote in article <01bbe5e6$75a1d700$0e433a82_at_gorbonosov.swarthmore.edu>...
> Hello everyone,
> The task I'm trying to accomplish is to run a procedure in background, so
> that I have control back to the Form/SQL prompt, once the job is
 submitted.
> So far I haven't been able to do so. I tried to run the procedure from
> "AFTER INSERT" trigger - no success, and with DBMS_JOB - no success; in
> both cases, I loose control of the Form until procedure is completed. Are
> there any other ways to do this?
> Thanks in advance.

I solved a problem like this, by calling Reports and having a BEFORE REPORT doing all the heavy stuff, like calling a stored procedure, that took around 10 minutes to run. The report just writes ONE word, and contains no selects. Write to destination FILE, filename "/dev/null".

I extended this feature with DBMS_PIPE, so that forms had a pct-bar telling me how far it had come in it's processing. The user could cancel the process by pushing a Cancel button in Forms, which in turn sendt another message via DBMS_PIPE, telling the stored procedure to abort before the next loop.

-- 
// Complete Data Service
// Peter H. Larsen
// PETLARS_at_IBM.NET