| Forms 6i to 11g migration issue [message #634884] |
Tue, 17 March 2015 09:00  |
dev_777
Messages: 32
Registered: June 2010
|
Member |
|
|
We converted our forms 6i to 11g.
We now notice that the go_block; execute_query; does not work.
Does not even throw out an error.
Did anyone have any experiences like this after converting from 6i to 9i then to 11g. Is there an settings on the block properties that require change.
[Updated on: Tue, 17 March 2015 09:28] Report message to a moderator |
|
|
|
|
|
| Re: Forms 6i to 11g migration issue [message #635143 is a reply to message #634971] |
Mon, 23 March 2015 01:00  |
dev_777
Messages: 32
Registered: June 2010
|
Member |
|
|
joy_division wrote on Wed, 18 March 2015 14:31go_block needs a block name.
OOps,typing error, yes we do have the block name
go_block('CUST');
execute query;
However, when we created a new button on the canvas with the above code behind the button, the the block queries.
We then copied all the code from the original button and stuck it in the new button - it does not work.
[Updated on: Mon, 23 March 2015 01:01] Report message to a moderator |
|
|
|
|
|
| Re: Forms 6i to 11g migration issue [message #635165 is a reply to message #635147] |
Mon, 23 March 2015 09:48 |
 |
CraigB
Messages: 386
Registered: August 2014
Location: Utah, USA
|
Senior Member |
|
|
Have you double-checked the block properties to ensure the block is still configured as a Base Table Block (eg: Database Data Block=Yes, Query Data Source Type=Table, Query Data Source Name=Table Name or is blank [if the block name is the same as the table name], etc)?
Have you tried running the form from the Forms Builder in Debug mode to see if there is an exception that is not being displayed?
As others have mentioned, it would be good to see the full Trigger code, not just an excerpt.
Craig...
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
