Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Oracle Forms (MOSC)

Bypass QUERY_ONLY inheritance when using CALL_FORM

Oct 30, 2013 11:08PM edited Oct 31, 2013 1:28AM in Oracle Forms (MOSC) 3 commentsAnswered

My company currently maintains a customer's application built on Oracle Forms 11gR2.

And we face the following issue:

Logged user has

QUERY_ONLY rights on Form_1
NO_QUERY_ONLY rights on Form_2

When they navigate from Form_1 to Form_2, CALL_FORM is being used
Thus, Form_2 inherits the QUERY_ONLY mode from Form_1 (as specified by Oracle Forms Documentation)

But we want to:

Keep the navigation (with CALL_FORM)
Have Form_2 be opened in NO_QUERY_ONLY mode anyway

Is there any known workaround for this usecase?

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month