0 
0 During our session on the Future of Oracle Designer yesterday I had a conversation with Josef Megens of Oracle Consulting and told me of a trick conceived by Mark Vahsen (formerly of Oracle) to ensure that post-generation changes could not be overlooked after generating a form.
The trick is this: include a program unit called POST_GENERATION_CHANGES in each form – or rather in each Module Definition in Designer – that requires post-generation changes. Make sure that this program unit contains a description of all post-generation changes. Also make sure that it does not compile! This means that when a developer generates the form and forgets to apply post-generation changes, compilation of the form will fail with an error message saying something like ‘Compilation of POST_GENERATION_CHANGES failed’. This should be a clear indication to the developer that he or she should apply the post generation changes.
Related posts:
Enabling Role-based security management in Oracle Designer 6i/9i/10g through the Repository Object Browser Great Oracle Forms 'plugin' – multirecord table column resize/sort/move around 
Poor man's VPD – Virtual Private Database before 8i and in Standard Edition Databases Aspect Oriented Programming (AOP) in PL/SQL – Is it hot? Is it cool? Or utterly useless? Dynamic SQL Pivoting – Stealing Anton’s Thunder