:system_record_status [message #118383] |
Wed, 04 May 2005 16:34 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
yemmy111
Messages: 1 Registered: May 2005 Location: uk
|
Junior Member |
![yemdoks](/forum/theme/orafaq/images/yahoo.png)
|
|
How do i set
system.record_status to query mode from insert mode
Have tried using the set_record_property but this didnt work.
Does anyone have any idea ???
|
|
|
Re: :system_record_status [message #118404 is a reply to message #118383] |
Wed, 04 May 2005 21:30 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](/forum/images/custom_avatars/67467.jpg) |
djmartin
Messages: 10181 Registered: March 2005 Location: Surges Bay TAS Australia
|
Senior Member Account Moderator |
|
|
Go to http://www.oracle.com/technology/documentation/forms.html. Find 'Form Builder Reference'. Download it and search for 'set_record'.
Quote: | SET_RECORD_PROPERTY restrictions
The following table illustrates the valid transition states of a record.
Current Target Status
Status
NEW QUERY INSERT CHANGED
NEW yes yes1 yes2 no
QUERY yes4 yes no yes
INSERT yes4 yes3 yes no
CHANGED yes4 no no yes
1 Adheres to the rules described in footnotes 2 and 3.
2 This transition is not allowed in query mode, because QUERY and INSERT are not valid in query mode.
3 If this transition is performed while Runform is running in Unique Key mode and not all of the transactional
triggers exist, then you must enter a valid value in the ROWID field. Put another way, if you are
connected to a non-ORACLE data source that does not support ROWID, but you are using a unique key,
you must supply the key for a record that goes from Insert to Query, in one of the transactional triggers,
either On-Lock, On-Update, or On-Delete. Otherwise Form Builder returns an error.
4 Records that have been changed but not yet committed or cleared cannot be assigned a status of
NEW.
|
Hope this helps.
David
|
|
|