| getting message for every record while pressing down arrow [message #290216] |
Fri, 28 December 2007 00:43  |
venkatadeekshi
Messages: 17
Registered: October 2007
|
Junior Member |
|
|
Hi,
when i query the form and when I am going through the records by pressing the down arrow of the keyboard I am getting the message 'Do you want to Save the records' for every record.
How to avoid the message?
I developed the form in oracle applications and it is a master detail form which have a header block and lines block.
thanks & regards
Deekshit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: getting message for every record while pressing down arrow [message #290313 is a reply to message #290298] |
Fri, 28 December 2007 06:09  |
mintomohan
Messages: 104
Registered: November 2006
Location: India
|
Senior Member |
|
|
in the ON-POPULATE-DETAILS trigger of main block, you are calling a procedure Query_Master_Details
in that procedure you are doing an Execute_Query on the detail block.
is there a chance that the data in the detail block might have changed and the confirmation message to save the data is shown?
Minto
|
|
|
|
| Re: getting message for every record while pressing down arrow [message #290352 is a reply to message #290313] |
Fri, 28 December 2007 07:48 |
venkatadeekshi
Messages: 17
Registered: October 2007
|
Junior Member |
|
|
Hi minto,
I solved the problem. I removed the select statements which are fetching the project_number, task_number and organization_name from the post query trigger of Budget_lines block. The message is not coming now.
I added additional columns for project_number,task_number and organization_name .. so that during post-query event the values are picked up directly from the base table.
Anyway Thanks for your replies
Regards
Deekshit
|
|
|
|
| Re: getting message for every record while pressing down arrow [message #290386 is a reply to message #290352] |
Fri, 28 December 2007 12:05 |
 |
Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
I didn't review the form you attached, but - perhaps you'd be interested in the following idea: SELECT statement you used in the POST-QUERY trigger and replaced with ... what? I didn't quite understand this part of your message.
However, you might leave the trigger as it was (having the original SELECT statement) and "convince" Forms that nothing really changed by using the SET_RECORD_PROPERTY built-in. It would look like this:
set_record_property(:system.trigger_record, 'block_name_here', status, query_status); |
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
