Re: Forms 4.5 Question - HELP!!!

EXCELLENT!!! Thanks for that, it's a good solution. It has given me a few ideas.

I think that what I will do is, only allow the editing of a record through a "modal" window. ie. the user presses EDIT button to change record which presents a "modal" window with the record in it. The window will have an OK and a CANCEL button on it. OK commits the changes, CANCEL rolls back changes hence releasing database lock on record.

Regards,

Pol.

In article <C_gO4.36$cn.8122_at_wdc-read-01.qwest.net>,   "Mike Dwyer" <dwyermj_at_co.larImer.co.us> wrote:
> I got around this in one form by using a post-record trigger to
 detect the
> change status. If so, enable and make visible a save button and a
 clear
> button, tell the user to save or clear changes first, then raise
> form_trigger_failure. When either save or clear button is pressed,
 they are
> both made not-visible again. Of course, the user then has to re-do the
> navigation out of the record.
>
> It might be better to make the buttons permanent and just not allow
> navigation out of the block with a changed status.
>
> <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.
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Apr 28 2000 - 00:00:00 CEST