Re: Stopping sequence increments
From: DanHW <danhw_at_aol.com>
Date: 1997/07/03
Message-ID: <19970703034401.XAA00238_at_ladder01.news.aol.com>#1/1
Date: 1997/07/03
Message-ID: <19970703034401.XAA00238_at_ladder01.news.aol.com>#1/1
I suspect that the default_value property of the field is set to
<sequence_name>.nextval. If you remove this, and instead put in the
when-create-record for the block the code to get the next sequence value,
the problem will go away (If you want even tighter control, put the select
<sequence_name>.nextval on a pre-insert trigger, or in an table insert row
trigger).
Dan Received on Thu Jul 03 1997 - 00:00:00 CEST