Calendar enter query mode problem

I have successfully implemented the calendar utility supplied by
the demo.
However, has anyone figured out how to use it when in
enter-query mode? It doesn't work because you can't navigate
out of current block when in enter_query mode.

In your Exit button's WBP trigger, do this:If :System.mode = 'ENTER-QUERY' then
Exit_Form;
End if;
Exit_Form(No_Validate);To get the button to work while the form is in enter-query mode, it must be in the same block as the one being queried, or else you must set its Mouse Navigate property to No.

Similar Messages

Calendar in Enter-Query Mode

Dear All ,
i hv posted my problems before.
My. Calendar does not work in Enter-Query Mode.
It says 'Function Key Not Allowed' It's Because of the Code(Go_Block) in Get Date procedure in the date package.
Any Suggestion on this will be highly appreciated.

You will have to change the calendar code to reside in a separate Form and use CALL_FORM to pop it up. This will be valid in Enter-Query mode - You'll then pass the selection back in a Global variable.

[Solved] Problem with LOV and 'enter query' mode

Hi all,
I'm kind of new to Forms and I'm having some problems that I'm not being able to resolve. I already search it on the net, but nothing relevant came up. If anyone could help me I appreciated it.
In my form I have some fields, and in one of them I have a LOV, and almost everything works fine. I inserted data, changed it, deleted it and all it's ok.
But when I change to 'enter query' mode, when I try to search for data on the LOV field it ignores what I write.
That is, for it, it's the same if I make F11 -> write 'aaaa' -> ctrl + F11 or if I make F11 -> '%' -> ctrl + F11.
It behaves the same way, shows me all the records.
Probably I'm missing something basic, but I'm not getting it...
Thanks,
Ana

when you create a lov by wizard the lov and record group have always the same name..
the problem is that the item is NOT based in the tabe.
what kind of query do you execute if you choose something from a love which is not based on the db?
i mean, this item has no influence on the query of the table, so whatever you choose it's like a "select * from table"
i hope i was clear

Problem in enter query mode

Hello Oracle experts,
When I do some query in enter query mode more than the required no.
of rows are appearing in detail block. For example If we have only 2 rows in detail table corresponding to one row in master then only those two rows should appear in detail block during query which are related to the corresponding master block record. But more rows are appering. What may be wrong please guide.
Thanks in advance
Ajay

Hi Ajay,
Is your relation between the two blocks applied correct?
Grtz.

Prevent interpretation of special characters in enter-query mode

My problem goes as follows:
- forms version: Forms [32 Bit] Version 6.0.8.10.3 (Production)
- non-database item block.X, char
- block.X is filled in post-query trigger. The post-query logic cannot be integrated in a view because it uses procedures, and usage of a pipelined function + view is currently not allowed due to "internal restrictions". Put simply: all logic to fill the field must remain in the post-query trigger
- user wants the field to be queryable. This is achieved by storing the entered criterium in a variable in the pre-query trigger, and using it in the post-query trigger to exclude records. E.g.
pre-query ==> help_block.query_X := block.X;
post-query ==> if help_block.query_X is not null and block.X is null or not block.X like help_block.query then raise form_trigger_failure; end if;
- this works fine for "regular" search strings. However:
- whenever the search string starts with <, <=, >, >=, !, forms seems to interpret the leading characters before doing anything else. During pre-query, block.X is null, and as soon as I use it in pl/sql, I get FRM-40831: Truncation Occured: value too long for field. E.g.
user puts the following in block.X ==> '<X', so he wants to search for records with value '<X' (text; not 'smaller than ...')
pre-query => msg.show(block.X) ==> appears to be empty/null, but right after the message, I get FRM-40831 Truncation Occured: value too long for field ...
This only happens if < is the first non-space character in the search string.
Does anyone know of a way to prevent oracle from interpreting the <, <=, ... characters entered in enter-query mode?

I'm sorry for not making myself clear; I'll give it another go:
The problem is that, if I enter '<abc' in a form field in enter-query mode (so during creation of the "example record"), forms immediately interprets the < as 'smaller than' and does some obscure things with it (my guess: converting to a where clause, but since I'm using a non db field, this actually does nothing), and finishes by erasing the field contents (in the example record). In the pre-query trigger, I can no longer get the '<abc' and store it. I want one of the following:
- prevent forms from interpreting the '<' in front (same thing happens for !=, <=, >=, =, ...)
or
- capture the entered string ('<abc') before forms reacts to the '<' in front
Edited by: [email protected] on Feb 17, 2009 12:30 PM

Initial Value in Enter Query Mode

Hi Everyone,
If you ever need to set a "visual" default (or initial) value for an item in Enter-Query mode, here is one solution to accomplish this:
Create a WHEN-NEW-ITEM-INSTANCE trigger at the block level where the item is located. Make sure it can fire in Enter-Query mode.
WHEN-NEW-ITEM-INSTANCE
If :system.mode = 'ENTER-QUERY' AND :system.cursor_item = <YourItemName> AND <YourItemName> IS NULL Then
<YourItemName> := <TheInitialValue>;
End If;You may wish to play with the "Keep Cursor Position" property of the item should you want the cursor to go back to the item position it was when the item was left.

It seems that your solution described solves my problem expressed 2 months ago....
I'll try it out....
Thanks......
Sim

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.

Changing visual attribute in Enter Query mode

Hello, I want to change visual attribute of all items in the first record when the user presses button for Enter_Query. I want that the user sees that the form is in enter query mode and it "waits" for the input of criteria. My code (copied from Help and modified) in trigger WHEN_BUTTON_PRESSED:
DECLARE
cur_itm VARCHAR2(80);
cur_block VARCHAR2(80);
BEGIN
ENTER_QUERY;
cur_block := :System.Cursor_Block;
cur_itm := Get_Block_Property( cur_block, FIRST_ITEM );
WHILE ( cur_itm IS NOT NULL ) LOOP
cur_itm := cur_block||'.'||cur_itm;
Set_Item_Instance_Property( cur_itm, CURRENT_RECORD, VISUAL_ATTRIBUTE,'yellow');
cur_itm := Get_Item_Property( cur_itm, NEXTITEM );
END LOOP;
END;
where yellow is the name of my visual attribute.
The problem is that I need to press the button TWICE to color the record.
Can anybody help me with this problem?
Natasa

(Wrong forum).
The problem is that enter_query stops executing your procedure until
another action ist started by the user.
You must create a short-time timer before issuing enter_query and set
your colour scheme in the when-timer-expired-trigger.

Blocking some fields from entering in summary block in enter query mode

Hi ,
I have a data block where in some fileds have to be dynamically allowed to enter and some are not based on
a particular condition. The problem is whenever the forms enters enter query mode, all the fileds in the block are updateble. Even maually I tried to set/unset the property in forms using set_item_property, but the enter query mode was trying to overiride it and making updateble.
Please suggest a solution for this.
Thanks in advance.
Thanks,
Lohith

Try the below code
IF :SYSTEM.MODE='ENTER-QUERY' THEN
SET_BLOCK_PROPERTY('BLOCKNAME',INSERT_ALLOWED,PROPERTY_TRUE);
SET_BLOCK_PROPERTY('BLOCKNAME',UPDATE_ALLOWED,PROPERTY_TRUE);
SET_BLOCK_PROPERTY('BLOCKNAME',DELETE_ALLOWED,PROPERTY_TRUE);
you can set the item here too by using the below code
SET_ITEM_PROPERTY('BLOCK.ITEM_NAME',INSERT_ALLOWED,PROPERTY_TRUE);
SET_ITEM_PROPERTY('BLOCK.ITEM_NAME',UPDATE_ALLOWED,PROPERTY_TRUE);Regards
Moazam
Edited by: Moazam Shareef on Oct 6, 2010 6:10 AM

FRM-40200 and FRM-40501 in Enter-Query-Mode

Some strange behaviour in Enter-Query-Mode:
Although the help states
About Designing Forms for Querying+
+.. To make a "query-only" block, set Query Allowed to Yes and Delete Allowed, Insert Allowed, and Update Allowed to No. ..+
I get FRM-40200: Field is protected against update.
System.Mode says, we are currently in ENTER-QUERY.
Setting insert- and update-allowed to TRUE, I get
FRM-40501: ORACLE error: unable to reserve record for update or delete.
The entered character flashes and is erased immediately.
Any ideas?
Forms 10gR2
Items are base table, all transactional properties aund query_allowed are true, query_length is ok.
2 Things that happen before the initiation of the enter-query-mode:
. data-source is changed to another view; column names are ok.
. all block-items are disabled and not navigable at start-up of form and re-enabled and made navigable before entering the block.
The values of block and item-properties mentioned above are take at WHEN-NEW-ITEM-INSTANCE and no further trigger fire.

I think you are not meaning just the KEY-ENTQRY-Trigger, that to easy
IF INSTR(:SYSTEM.TRIGGER_BLOCK, '_DETAIL') = 0
+ AND :SYSTEM.TRIGGER_BLOCK NOT IN ('VZG_KOPF','KONTROLL','BUTTONS','TEMP')+
THEN
+ ENTER_QUERY;+
END IF;
.. but the rest is a lil bit, let's call it bulky; including pll and db-packageges.
I hoped to get a clue, if somebody has a similar expeience, in what direction to search. It's strange.
And, as I noticed today, it's not a problem of all forms of the app. Not even of all the forms called from the same "environment" (same globals, same menu-form from which they are opened). To me it looks like Enter-Query does not work in the forms where I switch the block-data-source from a view to a globally temporary table. That (this switching) is not a new feature and Enter-Query worked in the past. Althoug we had some changes in the temp tables in the last weeks there are no problems in querying the data in the forms. Recompilation of pll and fmb, no improvement. And either Enter-Query woks in a form or it does not.

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.

Do_Key in Enter-Query mode

Hello,
I have a WHEN-BUTTON-PRESSED trigger that has do_key('list_values') that brings a calendar. I use calendar.pll library. It works, when the system is in normal mode. But when the system is in enter-query mode it does not work. It says "Function key not allowed". What is the alternate solution, other than calling the calendar functionality from a new form?
Thanks in advance.
Arun.

try this out,
go_item('item_name');
execute_trigger('key-listval');
specify the item name for go_item

Starting form in Enter-Query mode disables some buttons on Smartbar

Whenn I run a form (on the Web) which starts in Enter-Query mode, the buttons "Execute Query" and "Enter Query" are disabled on the Smartbar. Also the corresponding menu options are disabled. Besides, it is psossible to use the appropiate keys (in my case: F7 and F8).
Has anyone experienced the same problem and is there a solution?
Let me know.
Thanx

Frank: Thats what i thought too -but i saw (in other Sources) that it could be done, but how..
Eugeniy I Duzhinskiy:
So, many Thanks to you. It works fine !!!!
(Its great to see there are some other Forms Users out there :) )

Triggers in enter query mode.......

Hello folks,
In enter query mode can make the when_validate_item trigger to fire????
I set the fire in query mode but it seems that it doesn't work.....

I am not sure what you want to accomplish in enter query mode within the when-validate trigger but the when-new-item-instance trigger will fire in enter query and may be a solution to your problem.

Calendar enter query mode problem

Similar Messages

Maybe you are looking for