Re: Commit changes? Yes/No/Cancel
Date: Tue, 21 Sep 1993 14:28:04 GMT
Message-ID: <CDpK6s.AGH_at_stortek.com>
In article Jxy_at_uk.ac.brookes, p0070621_at_oxford-brookes.ac.uk (Tommy Wareing) writes:
> In Forms 3, if a block is cleared with changes pending, a dialog box
> pops up asking whether changes should be commited, with options of
> Yes, No or Cancel.
>
> This is giving us synchronisation problems when we have two detail blocks
> to be committed in conjunction.
>
> Specifically, if user says commit on clearing the first block, then all
> the changes in both blocks are committed, and everything works.
> If they say cancel on clearing the first block, then the first block is
> not cleared, and code can detect this and abort.
>
> So far, so good...
>
> If they say No to committing the changes in the first block, then that block
> is cleared, and processing continues to the second block. Since this is
> uncommitted, the dialog box reappears, and the user is allowed to commit
> the changes in this block.
>
> Does anyone have a mechanism for determining whether the user answers No
> when asked if they want to commit their changes?
You can do this a couple of ways.
- Use the PRE-COMMIT trigger to catch this; check for empty blocks, or whatever needs to be done to ensure your data integrity.
- Create your own pop-up window like the Yes/No/Commit in which you know
exactly what the user answered. This is always a must when you use nonbase
table blocks.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - stasica_at_stortek.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -