Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Call_form query only issues

tony.gAug 2 2013 — edited Aug 2 2013

Hi

I haven't had a need to call a form as query-only for quite a few years and truth to tell I couldn't quite remember what the behavious is supposed to be.

Testing this with Forms 11g (11.1.2.0) it seems that any form fields that are directly mapped to database fields are unchangeable directly due to the forms running in query only mode.  However, any fields that have the property Database=No allow you to change their content if they have an updateable or insertable property set to yes.

This doesn't seem ideal, as if you call a field in query-only mode you would hope that all displayed fields are unchangeable.  However, you can kind of understand the issue as non-database fields will be populated by post-query or other field level validation triggers, and if they were unalterable through the keyboard, then maybe this would make them unalterable via the triggers too.

The mystery is that these forms are upgraded from Forms 4.5, and my client is saying that in this legacy system, all of the fields are unalterable once data is queried (ie in Forms 4.5), which seems to be different behaviour to the way Forms11g is behaving now.

Can anyone validate or have knowledge that earlier forms versions might behave differently in query-only mode compared to Forms11g please?

rgds

Tony

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 30 2013
Added on Aug 2 2013
1 comment
1,259 views