Forms & Query-Mode

Is there any way to query the data in Application Express Forms as we can do it in Oracle Forms Query-Mode (F7 begin query, F8 execute query)?

Hi,
Try going to the SQL Workshop. It allows you to query the data in your schema.
If you don't like navigating to SQL Workshop from the Application Builder, open a second browser for your queries.
Hope this helps.
Cheers,
Patrick Cimolini

Similar Messages

Oracle form query mode does not change color to blue

Hi, I have created a custom form and using query mode in it. However on hitting F11, the record does not change to blue, instead it turns white. Can someone please guide me as to what I should be doing to get this right?
Thanks for your responses.

The fact that it doesn't change color when you "Enter Query" mode tells me your Custom Form does not conform to Oracle Application Programming Standards. I recommend you visit the Oracle Applications Documentation web site, choose your EBS version and scroll down and look at the Oracle Applications User Interface Standards for Forms-Based Products and Oracle Applications Developer's Guide to ensure your Custom Form conforms to Oracle Standard.
Also, I suggest you always use the TEMPLATE.fmb (or if you can't find this form, use the APPSTAND.fmb) as the starting point of any Custom Form. This will ensure you have the minimum required objects and code in your form.
Hope this helps,
Craig B-)
If a response is helpful or correct, please mark it accordingly.

How to put the form in Query mode

Hello
Please let me know how to put the form or block in Query mode , so that when i run the form it should be in Query mode . I have seen properties of SET_FORM_PROPERTY and SET_BLOCK_PROPERTY but cannot find one
Thanks

QUERY mode? Did you mean, that you can only QUERY without changing data.
This is the QUERY-ONLY-mode, which can be started e.g. call_form
this is the help for that topic:
PROCEDURE CALL_FORM
(formmodule_name VARCHAR2,
display NUMBER,
switch_menu NUMBER,
query_mode NUMBER,
data_mode NUMBER,
paramlist_name VARCHAR2);
query_mode
NO_QUERY_ONLY (The default.) Form Builder will run the indicated form in normal mode, allowing the end user to perform inserts, updates, and deletes from within the called form.
QUERY_ONLY Form Builder will run the indicated form in query-only mode, allowing the end user to query, but not to insert, update, or delete records.

FRM-41361 Cannot navigate out of current form in Enter-Query Mode

Hi All,
I am getting the FRM-41361 error in the bottom message area when opening a form from the function navigator. The issue does not exist when opening the form from the application homepage. The form is loaded in enter-query mode, and the enter_query command is in the WHEN-NEW-FORM-INSTANCE trigger. I have checked all triggers that fire after this point for any type of navigation but do not see any. The interesting thing is, if I put a fnd_message.set_string and fnd_message.show just before the enter_query call to debug, the issue goes away entirely.
Is it possible there are security triggers firing after the form is loaded into enter-query mode that could be causing this and that the fnd_message calls are indeed buying time for those triggers to complete before the enter_query call?
Any help/advice is appreciated. Thanks!
Dan

Yes, when I looked through the triggers I made sure to look for go_block and go_item calls as well as any calls to leave the form.

Open form in query mode

I want to be able to open a form in query mode - is there any way to set this?
I am using Designer and Headstart.
Thanks

Hi Cathy,
You can do this. See the help topic: About the startup query mode of generated forms.
Rgds
Susan
Oracle Designer Product Management

How to display LOV on web in ENTER-QUERY mode with form or block query only.

Hello all
How can I display lov automatic on the web in from enter-query
mode in form or block query only mode.
thankx

If I understand correctly your explanation, your called form
fails to activate the LOV in enter-query mode when it is deployed
and test on the browser.
So lets proceeed like this, to make it work in all environments,
let us programetically activate the LOV.
HOW?
In the called form, write in the WHEN-NEW-ITEM-INSTANCE TRIGGER
at block level (if have more than one LOV)
IF :SYSTEM.MODE = 'ENTER-QUERY' THEN
IF get_item_property(:system.cursor_item,lov_name) IN ('YOUR
LOV1', 'LOV2' etc) THEN
IF SHOW_LOV(get_item_property(:system.cursor_item,lov_name))
THEN
NULL;
END IF;
END IF;
END IF;
The above code maybe tweak to suite your need and condition.
This way, we explicitly make the LOV appear in ENTER-QUERY mode
whenever the user clicks on an item with an attached LOV.
Hope this helps.
Mohammed R.Qurashi

Query mode of Master Detail Form

I have a master-detail form.
I'm passing parameters to that form to autoquery data.
Everything works fine but "Next" button in a detail block.
I'm getting:
An unexpected error occurred: ORA-06502: PL/SQL: numeric or value error: NULL
index table key value (WWV-16016).
After autoquery LASTIN_SET variable of DEFAULT block is set "5" (number of rows in detail block).
When I click on "Next" button LASTIN_SET variable is set to "0" instead of "5" and that causes a problem.
So, somehow LASTIN_SET is not preserved between clicks.
In fish_size_form master-detail form
... before displaying the page
shrimp.p_set_parameter_fish_size(p_session,
p_block_name,
p_object_name,
p_instance,
p_event_type,
p_user_args
This is a code of shrimp.p_set_parameter_fish_size
p_session in out nocopy portal92.wwa_api_module_session,
p_block_name varchar2,
p_object_name varchar2,
p_instance varchar2,
p_event_type varchar2,
p_user_args varchar2
is
sess_store portal92.wwsto_api_session;
status varchar2(80);
station varchar2(80);
date_time varchar2(80);
sample varchar2(80);
species_code varchar2(80);
form_state varchar2(100);
begin
form_state := p_session.get_value_as_varchar2(
p_block_name => 'MASTER_BLOCK',
p_attribute_name => '_FORM_STATE');
if form_state = 'QUERY_AND_SAVE' then
sess_store := portal92.wwsto_api_session.load_session(
p_domain => 'sfnrc',
p_sub_domain => 'shrimp');
status := sess_store.get_attribute_as_varchar2(p_name => 'status');
if status = 'apply' then
station := sess_store.get_attribute_as_varchar2(p_name => 'station');
if station is not null then
p_session.set_shadow_value(
p_block_name => 'MASTER_BLOCK',
p_attribute_name => 'A_O_S_M_O_STATION__ID_K',
p_value => '='||station,
p_language => portal92.wwctx_api.get_nls_language );
end if;
date_time := sess_store.get_attribute_as_varchar2(p_name => 'date_time');
if date_time is not null then
p_session.set_shadow_value(
p_block_name => 'MASTER_BLOCK',
p_attribute_name => 'A_O_IN__SAMPLE_IN__DATE_TIME_K',
p_value => '='||to_char(to_date(date_time,'yyyy/mm/dd hh24mi'),'yyyy/mm/dd hh24:mi'),
p_language => portal92.wwctx_api.get_nls_language);
end if;
sample := sess_store.get_attribute_as_varchar2(p_name => 'sample');
if sample is not null then
p_session.set_shadow_value(
p_block_name => 'MASTER_BLOCK',
p_attribute_name => 'A_OBSERVED_IN__SAMPLE_NUMBER_K',
p_value => '='||sample,
p_language => portal92.wwctx_api.get_nls_language);
end if;
species_code := sess_store.get_attribute_as_varchar2(p_name => 'species_code');
p_session.set_shadow_value(
p_block_name => 'MASTER_BLOCK',
p_attribute_name => 'A_S_I_PROJECT_SPECIES_CODE_K',
p_value => '='||species_code,
p_language => portal92.wwctx_api.get_nls_language );
sess_store.set_attribute(p_name => 'status',p_value => 'done');
sess_store.save_session;
p_session.save_session;
fish_size_form.wwv_master_gensys_1(
p_block_name => p_block_name,
p_object_name => p_object_name,
p_instance => p_instance,
p_event_type => p_event_type,
p_user_args => p_user_args,
p_session => p_session );
end if;
end if;
end;
What I'm missing here.
Aantoliy.

Say, I click on Update Push button. This will invoke a LOV that will occurs 5 times and then display the header and detail record.
Even if, I am able to get the records in the canvas, I am not able to update the records of the master. The record_status is in INSERT mode of the header block. Interestingly, if i click 2nd time on update button and then get the records after executing LOV, the query enters the query mode and I am able to update the records then.
Please suggest how to overcome the problem on a sigle click on UPDATE button.

How do I get and pass Master-Detail rowid to another form in query mode?

I am trying to get the rowid of my master record passed to
another form in query mode. This is necessary because, I need to
have a way to show other detail tables for my master record. I
have been successful in calling the other forms, but only if I
hard code the rowid(or Primary Key).
Ultimately a "Tabbed" HTML table for each supporting detail
table that I have would be perfect. Any help would be greatly
appreciated. Thanks.

correct me if I am wrong, is this a 9iAS (Application Server)
related question? This forum is for 9iAS only.
Regards,
--Tao

Developering ADF form in query mode (Oracle forms simulation)

Hi,
we have a requirement for developing the existing Oracle form using Oracle ADF. The existing Oracle form displays the form in query mode by default. We can enter the search criteria in any of the text fields and then execute query to get the results. If the user does not enter any search criteria, then the form loads specific record based on default criteria into the form. Could you please help developing similar form using ADF.
At present I created the view object with one bind variable and dragged the view as ADF form to the jspx page. Then I am launching the form in query mode (executing the find method on the view object using operation binding at the time of loading the page). After entering the query criteria in the form, If I click on a button I am executing a method in the managed bean. In the managed bean I am executing the "Execute" operation on the view and it is working fine.
But my problem is if the user does not enter the search criteria I have to pass default parameters to the view object and return the default record in the form.
Can you please help in resolving the issue.
Thanks and Regards,
S R Prasad

Hi Frank,
Thank you for providing information. I created the query panel with the table by dragging all the named criteria. But this is not the look we are expecting for this form. As we have to deveop ADF form with the same behavior as oracle forms, the user must be in a position to edit the data in the same field as that of query field.
As an example, we have to design a form for Dept table. We have to display all the columns of the dept view in the form at the time of launching the form in query mode. Once the user enters any search criteria in the form, we have to perform search and display the record(s) matching the query criteria in the same columns displayed in the form. User should not see any changes in the form layout.
If the user does not enter any data in the form, then we have to display the record(s) in the form with the specific department id(This department id can be calculated based on the data in another table).
Can you please help us in resolving the issue.
Thanks and Regards,
S R Prasad

F11(Query mode) and Execute Query in Oracle Forms

Hi Experts,
I am working with EBS11.5.10.2 and database 9i. I am working on forms, i am new to forms.
Could somebody help me how to achieve F11(query mode) functionality in APPS forms.
Thanks in advance.

Hello,
Wrong forum. Ask the Personalization question in the dedicated E-Business Suite forum.
Francois

Calling another form when current form is in query mode

I have a form that is in query mode. When I select a menu option that calls another form through new_form, I get the error 'FRM-41009: Function key not allowed. Press Ctrl+F1 for list of valid keys.'
I would like trap this error, cancel the query and invoke the new form. I have tried to do this by code similar to this:
if :system.mode = 'enter-query' then
exit_form ;
end if ;
new_form('someform') ;
(since exit_form in query mode is supposed to cancel the query).
But in this case, the trigger ends with the execution of the 'exit_form' statement.
Any help would be greatly appreciated.
Thanks and regards,
Rajesh Jayaprakash
[email protected]

I think the following will work:
When you call the EXIT_FORM builtin, Forms cancels out of Query Mode but also stops the current PL/SQ execution - which is annoying.
I believe, though, that the WHEN-WINDOW-ACTIVATED trigger will fire on your Form. Therefore, you can:
1) Set a Global Variable or PL/SQL packaged variable just before you call the EXIT_FORM builtin then
2) Test the value of the Global Variable in the WHEN-WINDOW-ACTIVATED trigger and perform the CALL_FORM there.
3) Even better, put the CALL_FORM and associated parameters into a Program Unit on the Form - then you can call it from either the original trigger or the WWA trigger as necessary.
If this does not work, you could resort to:
1) Set a Global Variable just before you call the EXIT_FORM builtin
2) Initiate a TIMER
3) Call the EXIT_FORM builtin
4) In a WHEN-TIMER-EXPIRED trigger, check the value of the Global variable. If it's set, Call the Form you want to call
5) Again, put the actual CALL_FORM in a Program Unit so it can easily be called with the correct parameters from wherever you need to call it.
It's annoying that you need to go to these lengths to perform what seems to be such an easy task!
If anyone knows any better ways of achieving this, please add another reply!

Hotkey "Create Record" while the form is in enter-query-mode

pressing the hotkey F6 for create-record while the block is in enter-query-mode results in the error - message:
Function key not allowed. Press Ctrl+F1 for list of valid keys.
The error-occurs although I created a trigger KEY-CREREC. The trigger isn't executed
In older Forms versions the behaviour was different. Is there a way to let the form work like in the old versions?

thnx for reply.Problem not solved.
i m trying to assign the value of text item to a variable in pre-query trigger. i m able to get the value into variable when the string in the text item does not startwith <,>,=. but when the string starts with any one of the operator (<,>,=) it gives error.
lenth of variable is 1000 charaters, and text item's max leanth is just 4 charactres.

Exiting form after being in query mode

Hi guys,
Having an issue with some forms after migrating from forms version 6i to 10g. Learning as I go along.
Forms which startup in query-mode seem to have an issue when closing - all have two blocks - one block is utilised through user query and the other (like a child) displays the query results and can be updated from here. If the user does not enter a query they can cancel it using exit_form which works fine.
After a query has been completed the system mode returns to 'normal' mode (which I can see through debugging by entering messages/pauses throughout the code). However when exiting the application breaks with error FRM-92100. I have had this problem before with regards to exiting forms but I got round this by having an open window (acting as a parent or root window) in the background which is not closable. Been tweaking the form all afternoon including using exit_form(no_validate) and other changes. By commenting out enter_query and execute_query commands the form closes as normal without issue which means it is related to query mode or something along these lines.
If anyone has any ideas or pointers on how to move forward with this it would be much appreciated.
Cheers,
Robin

Guys,
Thanks for the replies.
The form currently uses exit_form twice in order to close the query mode and I receive a message "query cancelled" to confirm this.
I have also tried - and retried for the benefit of confirming this - the code you have mentioned u3 - using it in the when-window-closed trigger. I chose <option> to be no_validate.
The main app is opened from a webpage. Forms are opened from a menu which is attached to all forms. The code that opens the forms is open_form (i.e. not call_form or new_form) for modal reasons.
The application is disconnected straight after exit_form is used - its as if coming out of query-mode to normal causes this as I said before closes gracefully when I remove the enter_query command.
As for the error message itself here is a fuller picture:
FRM-92100: Your connection to the server was interrupted. This may be the result of a network error, or a failure on the Server. You will need to reestablish your session.
Details...
java.lang.NullPointerException
at oracle.forms.handler.TextComponentItem.selectionChanged(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextComponent._fireSelectionChanged(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextComponent.select(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextField._selectAll(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextField.processFocusEvent(Unknown Source)
...AND SO ON!
Hope this gives a better picture of what's going on :)
Robin
update - There is a 'dirty' workaround to this problem - if i minimize the window (change its state in any way) after the mode is back from query-mode to normal THEN close the window it closes gracefully.
Edited by: Robin84 on Sep 10, 2008 10:03 AM

Open multiple forms, few in Enter-Query mode

Hi All,
I want to open multiple forms from a form using open_form built-in. If user clicks on different items of the parent form different child forms are invoked.
But if one child form is opened in Enter-Query mode (I have 'enter_query;' in its when-new-form-instance) it does not allow to put focus back on parent form and invoke other forms until I execute_query in child form or close the child form.
Waiting for your replies. Thanks in advance.
Regards
Mona

Hi Friends,
Has anybody ever faced this problem. Please reply.
Regards

Forms that start in enter query mode freeze on exit

When a headstart form is called from
a menu and the first thing it does if go into
enter query mode the form will not exit properly, causing the orginal form to hang.
Is there any work around for this apart from taking enter_query out of the when_new_form_instance trigger ?

We have a similar problem with a Headstart generated application. We are unable to pinpoint it entirely to forms that start in enter query mode as:
a) forms that don't start in enter query mode also hang; and
b) not all forms that start in enter query mode do hang.
The problem doesn't seem to affect a form consistently, as one day it will hang on the first use, the next it will work for several hours.
When a new form is selected from the menu the toolbar is not shown, the 'start' form disappears and the application hangs. It is then necessary to close the application using Task Manager.
The good news is that this only seems to happen in our development environment (Windows NT 4) and not in our live environment (Hydra).
We are working with Headstart v2.1.2.0.1,
Designer v2.1.24.1.0 and Forms v5.0.6.11.0.

Forms & Query-Mode

Similar Messages

Maybe you are looking for