I'm sitting at LA airport on my way to the ODTUG conference, having been up for just on 24 hours with 20 hours flying time behind me. Unfortunately my UA flight to Denver has been canceled, and now I'm waiting 7 hours for the next available flight direct to New Orleans. Being one of those people who doesn't really sleep on planes, and certainly not in airports, I'm calculating I'll be up for just around 38 hours before I finally hit a bed.
(+1 day edit note: oh well, it was only 34 hours in the end, not too bad really, can't complain ;)
Sheesh, one day a flight through the US will go without a hiccup.
Anyway, this leaves me more than a couple of minutes to let you know Penny Cookson and I are happy to announce our next Oracle Tech Network article, Return to Formsville has been published. I've listed a blurb of the article below which hopefully will catch your interest.
Some readers might be surprised that we've published an article on Oracle Forms given my blog interests in JDeveloper. In fact my boss Penny Cookson and I come from a strong Oracle "core-tech" background of Designer 100% generation, meaning a substantial background in Oracle Forms programming, and even a smattering of Oracle Headstart in my case. Thus why my last 2 OTN articles have been based around legacy artefacts from Oracle Designer and Forms; I'm interested in boot-strapping that old code base into something we can still use in the future.
For those interested, the other previous OTN article was Integrating the Oracle Designer Legacy Table API with Oracle JDeveloper 11g ADF Business Components.
I can't say I have any interest on moving back to Oracle Forms, but this attitude doesn't pay the bills, and from time to time myself and Penny and other Sage employees still maintain and extend the odd Oracle Forms system here-and-there. Sage Computing still in fact offers Oracle Forms training in Australia.
A final note of thanks to Justin Kestelyn and the OTN team for assisting us in the publication of this new article.
Returns to Formsville
New programmers moving into Oracle sites running legacy Oracle Forms and Oracle Designer applications face many challenges. New programmers rely heavily on their senior counterparts to teach them how to structure their applications, as well as the benefits of such structures from hard-earned experience. There are certainly plenty of best practices around for Oracle Forms, and Oracle Designer gave its own particular stamp to Oracle Forms architecture. Yet at many sites, senior programmers have moved on, leaving their successors guessing why applications are structured as they are. With the pressure to fix mounting maintenance issues, the elegance of the original solutions can be jeopardized.
For those starting their Oracle Forms journey, this article attempts to explain the key architectural concepts that are common to many Oracle Forms– and Oracle Designer–based applications, including their benefits and how you can use them to your advantage. In particular, the article will focus on:
* A simple Oracle Forms trigger architecture
* A flexible Corporate-Application-Form Oracle Forms library architecture
* Extending the approach to forms generated from Oracle Designer
* Oracle Designer artifacts, including the table API, cg_ref_codes, and journal tables.