OraFAQ Forum: Forms » restrict standard save functionality

Home » Developer & Programmer » Forms » restrict standard save functionality (forms6i,apps11.5.10)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

restrict standard save functionality [message #512518]

Mon, 20 June 2011 15:00

rajendaroracle
Messages: 80
Registered: May 2011
Location: India

Member

Hi

how can we restrict standard save button functionality in custom form?

Report message to a moderator

Re: restrict standard save functionality [message #512521 is a reply to message #512518]

Mon, 20 June 2011 15:15

joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA

Senior Member

remove the menu.

Report message to a moderator

Re: restrict standard save functionality [message #512599 is a reply to message #512521]

Tue, 21 June 2011 02:43

Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

How would you like to restrict "standard save button functionality"? It performs COMMIT. So, if you restrict it, what would it be? How would you save changes?

Report message to a moderator

Re: restrict standard save functionality [message #513315 is a reply to message #512599]

Sun, 26 June 2011 13:38

rajendaroracle
Messages: 80
Registered: May 2011
Location: India

Member

I have created control item(SAVE) for save functionality. Based on that i will submit conc.program through form. can we submit concurrent program through standard save functionality.then i will go for that.is it possible?

Best regards,
rajendar

Report message to a moderator

Re: restrict standard save functionality [message #513317 is a reply to message #513315]

Sun, 26 June 2011 15:39

Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

This smells like an Oracle Apps. question ("submitting a concurrent program"). If that's so, the following might not be true there.

Anyway: your SAVE button (is it a button?) and its WHEN-BUTTON-PRESSED trigger are supposed to do what KEY-COMMIT does. So, if you create a procedure (let's call it PRC_COMMIT) and put all your code in there, and then call PRC_COMMIT from both WHEN-BUTTON-PRESSED trigger on SAVE button and KEY-COMMIT trigger, you might capture both events.

Report message to a moderator

Previous Topic:	Tabular Form Top Record
Next Topic:	forms not running on internet explorer

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Feb 03 10:51:16 CST 2025