2 Replies Latest reply on May 16, 2019 9:26 AM by Frank Hoffmann

    While compiling the form 6i to 12c then there is problem in Set_Window_Property


      Hi All,


      I'm Compiling the Oracle forms 6i code in 12C oracle Fusion Middleware then its displaying the popup by saying "Invalid value used in Set_Window_Property for window FRM-(41630)"


      Could someone can help me in identifying with same where need i make the changes



        • 1. Re: While compiling the form 6i to 12c then there is problem in Set_Window_Property
          Michael Ferrante-Oracle

          Please share the exact Forms version you are using.  If you are not using, you should consider using it.


          Please also share the exact line of code that is failing (the SET_WINDOW_PROPERTY line and related code).  Also include the complete error message and its text.


          If you are generating on the command line, it might be easier to troubleshoot from within the Builder.  Open the offending module in the Builder then press CTRL+Shift+K.  This should expose the same error and exactly where in the code it is having the problem.  That should help you to better understand what it is going on.


          And most importantly, if you are upgrading an app from 6 to 12, it is very important that you read the Forms 6i to 12c Upgrade Guide as it explains the differences between 6 and 12.  It also explains what code you may need to update.



          • 2. Re: While compiling the form 6i to 12c then there is problem in Set_Window_Property
            Frank Hoffmann



            are you compiling or running a Form? Usually these FRM-Errors come up during runtime.


            Dpending on what you are doing (calculating positions with Windows) you can get to negativ values in 12c.


            Example: get_window_property Returns 0,

            x:= get_window_property('ROOT_WINDOW',width);

            set_window_property becomes negative



            The best attempt to clarify this to is activate variables in the debug tab canvas of the forms builder, then set a debug point before this calculation and start forms in debug mode (one button debug). The Debugger in is the first stable 64 Bit Debugger and very powerful and useful to detect these Errors.



            Make sure you have IE11 with a 32 Bit Java plugin on your Client and a preference to your Formsserver like this:



            Debug break Points are made with a double-click in the Forms PL/SQL Editor on the left line like this

            When the Form started in debug Modus you will see a flashing Forms builder and the active debug Windows.


            Step through the Code with

            and watch the values that become negativ or invalid

            I guess you have trouble with the calculations of the "forms-mdi-window"