Re: Default values != new record

Mark Haston (mark_at_minarama.demon.co.uk) wrote:
: I have a v3 form with a master-detail setup.
: One field of the detail is populated directly with $$date$$ as default and
: another is populated with a default value via a pre-block trigger selecting
: a value into a control field and thence into the detail field via its'
: default value.
 

: The problem is unless I add something into one of the remaining fields (or
: change one of the defaults) Oracle doesn't think there's a new record there
: at all - I get "...no changes to commit." The doc says otherwise.

My Forms 3.0 was long ago, but unless I am mistaken, you won't have changes to commit unless you actually place a value into a database field with a direct assignment (or you could cheat and copy 'CHANGED' into the :SYSTEM.form_status variable, but I DON'T reccommend that.)

So, instead of using the defaul against the control field, select the value from the database into the database field -- this will give you a record to commit, if you want a new record each time the form is run. At least, it *should* :-)

: I have the sneaking suspicion that I'm missing something *real* obvious but
: for the life of me I can't see it. Can someone put me out of my misery please.

I think what I said above is fairly obvious, but I learned that long ago when trying to get defaults working in the first place. You seem to have taken the reverse of the learning path I followed :-)

: (I've mucked about with on-new-record and key-nxtblk [on the master] but,
: alas, no joy.)

Hey, don't ever let Oracle get you down. Otherwise, you'll be grumpy always :)

: --
: M

Good luck with your work

Jonathan Received on Thu Apr 27 1995 - 00:00:00 CEST