Re: Forms 4.5 Question - HELP!!!

Hi there

You can use it on When-validate-record trigger. YOu'll still get the error message saying illegal restricted procedure when using commit_form built-in. You can get around this problem by using timers. It really works. Just create a timer in when-validate-record trigger and use your commit_form built-in inside when-timer-expierd trigger. hope this helps.

Cheers...kasi

Jason Judge wrote:

> Can you set the validation scope to 'record'? It has been a while since I
> did this so the terminology is probably wrong, but I think you can set this
> property on the block, otherwise set it globaly when you enter the block.
> Using 'record' validation scope means that Forms handles ALL forms of
> navigation off the record and asks if you want to save - you do not need to
> put any triggers in or 'code around' this.
>
> This is just from memory - so the details are rusty, but look for
> 'validatino scope' in the manual. It is a property that can be changed at
> run-time as necessary.
>
> Regards,
>
> Jason Judge
>
> <pol15_at_my-deja.com> wrote in message news:8ebke8$9da$1_at_nnrp1.deja.com...
> >
> >
> > I want to detect if a user has "changed" a record before he navigates
> > "off" of it onto a different record, and give him the option to "save"
> > or not. ie. I want to give the option "Do you wish to save the changes
> > you have made? YES/NO/CANCEL".
> >
> > I want this alert to appear BEFORE the user actually navigates to the
> > new record, as I want to remain on the old record if they choose the
> > CANCEL option.
> >
> > I know I can use the system variable ":SYSTEM.RECORD_STATUS =
> > 'CHANGED', but I am not sure what trigger to use.
> >
> > The thing is, I want to issue a COMMIT_FORM command if the user says
> > "yes" to save changes, and Forms doesn't like this being used in the
> > triggers I have tried.
> >
> > For example, if I use the POST-RECORD trigger to prompt the user, then
> > I get the error "FRM-40737: Illegal restricted procedure COMMIT in POST-
> > RECORD trigger" if the user chooses to "save" their changes.
> >
> > NOTE: Oracle Forms produces a similar default alert when there are
> > unsaved changes to the current record set if the user tries to re-
> > query. I am trying to avoid this automatic message appearing by getting
> > the user to commit/rollback before the default appears.
> >
> > Can anyone shed any light on this problem?
> >
> > All help greatly appreciated.
> >
> > Pol.
> >
> >
> >
> >
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
Received on Mon May 01 2000 - 00:00:00 CEST