Oracle Error Frm-40401
[message #110906] Thu, 10 March 2005 19:35 rajesh Messages: 173Registered: November 1998 Senior Member I have updated a table from the form and written a update statement in the when-button-pressed standard.commit in oracle forms trigger. while the code is working fine and the table is updated but oracle forms commit no changes to save iam finding this error in the console frm-40401 no changes to save. pls help me why it is coming frm-40405 no changes to save and what affect it have on my form. i had suppressed this message by writing on-error trigger on form level. Report message to a moderator Re: FRM-40401 No changes to 40401 zip code save error [message #110911 is a reply to message #110906] Fri, 11 March 2005 00:39 djmartin Messages: 10180Registered: March 2005 Location: Canberra ACT Australia Senior MemberAccount Moderator The COMMIT (COMMIT_FORM) statement analyses the blocks that exist in your form. If you change a table independently from the declared blocks then the form does not think that it has any changes to save. Hence the message. Use 'standard.commit' this bypasses any checking and does just that which you asked - commit, now!! David Report message to a moderator Re: FRM-40401 No changes to save error [message #110919 is a reply to message #110911] Fri, 11 March 2005 01:52 raj_150879@yahoo.com Messages: 1Registered: March 2005 Location: india Junior Member Thanks for ur reply. iam able to do it now! thanks a lot. plz clarify one point.as you said that "The COMMIT (COMMIT_FORM) statement analyses the blocks that exist in your form. If you change a table independently from the declared blocks then the form does not think that it has any changes to save. Hence the message." sir, but i have written the update statement in the when-button-pressed trigger which is under the block .thus i think that i have change the table in the data block and not independently from the block. --excuse me if it seems stupid as iam a new user of D2K-- Use 'standard.commit' this bypasses any checking and does just that which you asked - commit, now Report message to a moderator Re: FRM-40401 No changes to save error [m
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Forms All PlacesDevelopment ToolsForms This discussion is archived 1 2 Previous Next 24 Replies Latest reply on Sep 26, 2008 7:48 AM by 611407 Go to original post This content has been marked as final. Show 24 replies 15. Re: FRM-40401 : No changes to save Forms Sep 24, 2008 8:01 PM (in response http://www.orafaq.com/forum/t/42156/ to 658893) Just 2 display items??? No other Database items? Thanks and Regards, Like Show 0 Likes(0) Actions 16. Re: FRM-40401 : No changes to save 611407 Sep 25, 2008 2:48 PM (in response to 658893) FRM-40401: No changes to save.Cause: No forms database records or fields were added or modified since the last apply or save. Caution: Unapplied database changes that were made through explicit sql https://community.oracle.com/thread/711966?start=15&tstart=0 (DML) are still applied, even when this message is displayed. Action: No action is necessary. Level: 5 Type: Error> So, if you have changed a database item on a database block then you should not see this error when you press save. The online help is not quite accurate on this I think, because you can set the record status to Query_Status after making changes and the form will treat it as if no changes have been made. If you have Set_Record_Property in your form then this could be the reason for the error. Are there any library functions called by your form, which might be doing a commit? -- I initially assumed that your problem was that the 40401 error was being displayed automatically. The code I posted above was supposed to replace any code which was committing the form. It was not intended to be put in the when-new-block-instance trigger, and whilst it is in there (and if you have 2 or more blocks in your form) it could actually be causing your problem. Edited by: u3 on Sep 25, 2008 3:47 PM Struck out text: not applicatble to the commit. Like Show 0 Likes(0) Actions 17. Re
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for https://www.experts-exchange.com/questions/20581963/'FRM-40401-No-changes-to-save'-Problem.html a Full Time Job Ways to Get Help Expand Search Submit Close http://oracleappsengineering.blogspot.com/2012/06/frm-40401-no-changes-to-save-fix_21.html Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > 'FRM-40401 No changes to save' Problem. Want to Advertise Here? Solved 'FRM-40401 No changes to save' Problem. Posted on 2003-04-10 Oracle Database 1 Verified Solution 9 Comments 7,187 Views Last oracle forms Modified: 2010-05-18 Hi exports, I developed a Oracle forms 6.0 application. I need to insert values to two tables, because the integrity constriants. I have to insert valuves to one table and commit, then insert values to the other table. The program runs good. But it always gives me 'FRM-40401 No changes to save' message. How to make the program does not show this no changes to message? Thanks a lot. John 0 Question by:yxj4276 Facebook Twitter LinkedIn Google LVL 2 Best Solution byAlbertYou Just set the message level to 5 or upper before you commit the changes. :SYSTEM.MESSAGE_LEVEL := '5'; commit; :SYSTEM.MESSAGE_LEVEL := '0'; Go to Solution 9 Comments LVL 2 Overall: Level 2 Oracle Database 2 Message Accepted Solution by:AlbertYou2003-04-10 Just set the message level to 5 or upper before you commit the changes. :SYSTEM.MESSAGE_LEVEL := '5'; commit; :SYSTEM.MESSAGE_LEVEL := '0'; 0 LVL 47 Overall: Level 47 Oracle Database 47 Message Active 1 day ago Expert Comment by:schwertner2003-04-11 You can also filter it in ON-MESSAGE trigger. You can suppress a particular message by checking the message_code, like: in ON-MESSAGE trigger: if message_code = 40405 then null; else message(mesage_code||': '||message_text); end if; The more complex case is when your form is called from another using OPEN_FORM. In this case the mentioned message appears not in the called form but in the calling form. The workaround is to use NEW SESSION parameter in OPEN_FORM. Alternatively use CALL_FORM. 0 LVL 6 Overall: Level 6 Oracle Database 6 Message
value between 0 to 20 where 0 allows all error messages to be displayed where as setting to 20 shows most important message. :system.message_level := 5; Use standard.commit instead of commit_form; at 5:37 AM Reactions: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Forms - Developer Errors 1 comment: Sridevi KSeptember 26, 2016 at 9:52 AMRegardsSridevi Koduru (Senior Oracle Apps Trainer Oracleappstechnical.com)LinkedIn profile - https://in.linkedin.com/in/sridevi-koduru-9b876a8bPlease Contact for One to One Online Training on Oracle Apps Technical, Financials, SCM, SQL, PL/SQL, D2K at training@oracleappstechnical.com | +91 - 9581017828.ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search this blog Welcome to Oracle Apps Engineering Having good exposure to Oracle Applications Technical R11i and R12, I am glad to start a blog to share the knowledge.I will keep posting new topics with the approaches used in technical aspect for the issues encountered.Hope this help newbie's and gives some quick reference to amateurs.Have a good day... Followers Amazon Deals Google Search Blog Archive ► 2016 (1) ► May (1) ► 2015 (16) ► November (3) ► October (3) ► September (2) ► July (2) ► March (6) ► 2014 (1) ► January (1) ► 2013 (14) ► December (1) ► October (1) ► September (2) ► August (2) ► July (1) ► May (2) ► April (5) ▼ 2012 (32) ► September (2) ► August (1) ► July (2) ▼ June (6) XML Publisher conditional formatting Set Org Context in Oracle Apps 11i and R12 Forms Trace / Diagnostics Oracle Apps FRM-40401: no changes to save Install font using XML Publisher Administrator Barcode in XML Publisher ► May (7) ► April (1) ► March (10) ► February (3) ► 2011 (3) ► April (2) ► February (1) ► 2010 (4) ► July (1) ► June (1) ► April (1) ► March (1) ► 2009 (2) ► December (2) Ethereal template. Powered by Blogger.