Uniface on GitHub
Product (releases and patches)
Reported Issues (old)
Fixes and Updates
We are trying to migrate our application from Uniface 9.7 to 10.3 but we are facing compilation errors in many of our forms ;
The problems seems to be linked to inheritance :
Our original Form has an entity with specific <Local proc> code in order to bypass the model entity local proc.
But after form migration when compiling we get errors because the form has in her module list the model entity local proc that should not have been there;
How can we avoid getting the entity default Local Proc in our form ?
Any idea ?
There is documentation in the Uniface 10 library on this subject:Migration to Uniface 10 > Pay Special Attention To ... > Inheritance and Compilation of Migrated Entries Inheritance and Compilation of Migrated Entries
The locally-defined entry log overlays the modeled entry definition.
So if you have local variations they will block the local proc.
Another idea is to work with defines and/or compile time constantsIn the modeled entity#ifdefined MYSWITCHentry testmessage/info "test"end#endif
Other example with compile time constant
trigger detail#if ("<$componenttype>" = "P") public web#elseif ("<$componenttype>" = "D") public web#endif#ifdefined UGEN1 clear/e "<UGEN1>"#else clear#endif#if ("<$componenttype>" = "P") webgen#endifend
Best regardsPeter BeugelSr. Technical Support AnalystUniface B.V.
© 2020 Uniface Privacy & Cookies | Privacy Statement | Legal