Oracle Forms

Maximum Records Displayed is new to 14.1.2, so this should not impact any modules that were upgraded from a previous version. At design-time, if you set this property to a value where at runtime, the last/bottom record may fall off the bottom of the canvas the warning you mentioned may be presented when generating. At runtime, it is your responsibility to ensure that the canvas size is increased as necessary to accommodate any rows that may fall off the bottom.

Reminder, Number of Records Displayed should be used to indicate how many records you want display at all times. Maximum Number of Records Displayed should only be used IF you plan to use Auto-Size Block or plan to programmatically change the Number of Records Displayed at runtime.

If what you are saying is that in a multi-record block you want to set one item to Number of Records Displayed = 1, you cannot do this when enabling Auto-Size Block or setting Maximum Number of Records Displayed.

This is not a bug.

Details about this new feature and many others can be found in the Forms 14c New Features guide. For this feature, refer to the section titled “Multirecord Blocks”. More detailed information about using this feature and its properties can be found in the Builder Help.

https://www.oracle.com/a/otn/docs/oracleforms-1412-newfeatures.pdf

Hi Michael,

So you got it right when you say, “in a multi-record block you want to set one item to Number of Records Displayed = 1, you cannot do this when enabling Auto-Size Block or setting Maximum Number of Records Displayed.” however, the first part is the only thing we're doing.

As you can see our block only has Number of Records Displayed to 10 while the new properties for the Maximum Records Displayed is 0 and Autosize Block is No. and so based on what you said or at least what I interpreted, I shouldn't be getting that error message, yet we're getting the error message.

The fix we have applied in this case is to move those buttons to a different single record block.

Thank you!

Got it, I just realized that the .err file is being created with these warnings, but I see the .fmx is being generated as well. When I saw those, I thought that no .fmx was being created.

This we have an internal build process to compile for Windows and Linux and it seems the warnings are splashing over the stderr. I'll probably have to make a change to confirm that if the .fmx is created, to ignore the error in that case and move the build process along.

Thanks again.

Hi Mike,

yes, the warning could be ignored, which could be done on linux batch mode very comfortable. If we mass - compile under windows, the batchmode don't hide the message. So we could not integrate Windows in our nightly build.

Is there any registry or hidden parameters to frmcmp to “ignore” these messages?

Thanks

Stephan

This should work. It can easily be added to a loop to compile all modules in a directory.

frmcmp.exe batch=yes window_state=minimize compile_all=yes <ADD ADDITIONAL ARGS HERE>

Hi @michael-ferrante-oracle
The workaround you mentioned does not work for use because we are about to start doing FADS deployments and FADS interpret those warnings as compilation errors, therefore the deployment is marked as failed.

Is it possible to instruct the compiler to ignore those warnings or not spit out the FRM errors?

This is going to be an issue when we integrate FADS with CI/CD because it will use FADS CLi to do the deployments.

Thanks

@gasparyyc With regard to using FADS and this warning condition, we are aware of the issue and developers are investigating it in bug 37693539 We believe we understand the root of the problem and hopefully will be able to correct it very soon.

If you already have a Service Request with Support regarding this issue and they have not already mentioned the above bug, feel free to refer to it so they can follow up and provide you status updates.