Re: Commit Problem

See below.

Scott wrote:

> G'day
>
> I have finally found the cause of my commit problem.
> If I use the default smartbar on the form, and execute and scroll
> through the master records that way, insertions and deletions can be
> made in the detail block no prob.
>
> But I'm populating the master block with an LOV, which executes the
> query on the tabular detail block.
> Oracle seems to think that this master record has now been changed, and
> when the commit command appears, it tries to commit the master block as
> well - and unique key contraint gets violated.
>
> Can anyone see a solution - ie - be able to search for the master
> record, without having the commit problem?
>
> ps - does anyone know the built-in for the e-mail command?

Hi, to avoid the commit you does not want you can make a master block to be not a database block with all detail block processing by your own code or you may
perform a query on a database master block just after your LOV put a value customer choose (in KEY-Listval trigger, for example). The last way, I guess, you need an extra temporery storage field to accept the value from LOV of the master block's field.

Hope this helps Alexander Received on Mon Oct 09 2000 - 06:22:01 CDT