Home » Developer & Programmer » Forms » Detail block behavior (Forms 6i)
Detail block behavior [message #597241] Tue, 01 October 2013 23:27 Go to next message
m.abdulhaq
Messages: 136
Registered: April 2013
Location: Ajman
Senior Member
I have a master detail block based form, sometimes its very strange that upon saving the record on current row of detail record, the record disappears but when i exit and re query the item is actually saved.But when i keep the cursor on next record which is blank and save it , there is no problem.Something to do with properties.Kindly advice.
Re: Detail block behavior [message #597246 is a reply to message #597241] Wed, 02 October 2013 00:17 Go to previous messageGo to next message
Littlefoot
Messages: 19889
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
The main problem is in one word: SOMETIMES. What does it mean? Are there only 2 cases (1: you are in the empty record -> no problem. 2: you are in any other record -> it disappears)?

If you were on later Forms version, you could run the form in debug mode and follow its execution path. Now, on 6i, you'll have to put MESSAGE built-ins into your PL/SQL code units so that you could see - step by step - what the form exactly does and spot the moment record disappears.

Alternatively (and much less costly) is to execute query in detail block after commit, such as
commit;
go_block('detail_block');
execute_query;

Hopefully, you won't even notice that anything happened.
Re: Detail block behavior [message #597254 is a reply to message #597246] Wed, 02 October 2013 03:03 Go to previous messageGo to next message
m.abdulhaq
Messages: 136
Registered: April 2013
Location: Ajman
Senior Member
Sorry littlefoot , to be more precise while i am on detail record which is of type multirecord, after entering the complete first row or line and when i save that line disappears, when i requery the record will not appear ,i have to close the form and re open it again.then record is appearing.
Re: Detail block behavior [message #597255 is a reply to message #597254] Wed, 02 October 2013 03:09 Go to previous messageGo to next message
cookiemonster
Messages: 11285
Registered: September 2008
Location: Rainy Manchester
Senior Member
does the detail block have any list items where the values of the list are changed programmatically?
Re: Detail block behavior [message #597267 is a reply to message #597255] Wed, 02 October 2013 05:52 Go to previous messageGo to next message
mughals_king
Messages: 390
Registered: January 2012
Location: pakistan
Senior Member
check this sample .fmb master & detail block


regard
mughal

[Updated on: Wed, 02 October 2013 05:55]

Report message to a moderator

Re: Detail block behavior [message #597316 is a reply to message #597255] Thu, 03 October 2013 02:38 Go to previous messageGo to next message
m.abdulhaq
Messages: 136
Registered: April 2013
Location: Ajman
Senior Member
no cookiemonster.
Re: Detail block behavior [message #597319 is a reply to message #597316] Thu, 03 October 2013 03:00 Go to previous message
cookiemonster
Messages: 11285
Registered: September 2008
Location: Rainy Manchester
Senior Member
Ok then you're going to have to debug your form to work out what's going on.
As LF already suggested - put messages in each form trigger / program unit so you can see what gets fired when you save the records.
Use get_block_property(<block name>, last_query) to check what query the form submits to the DB when you try to requery the data and don't get it.
Previous Topic: file transfer form server directory to client
Next Topic: organization chart (merged)
Goto Forum:
  


Current Time: Sat Dec 20 08:49:38 CST 2014

Total time taken to generate the page: 0.07699 seconds