Moving from client server architecture to R12 based domains could be quite challenging for Oracle developers, especially those who have spent years, enjoying the flexibility of testing forms modules from the local development machines prior moving the “working” modules to the production instances.
Let us see the general development scenario for R12 instances.
- From 10g forms, connect to database
- open TEMPLATE.fmb and save as “XXMYFORM” etc
- Then keep on adding the elements
Now, move the form module to $AU_TOP/forms/US and compile it to respective application repositories
Create form, menu items…
A long list and the most frustrating is keeping on FTP the slightly modified forms module to the R12 instance to compile and testing.
We have came across a quick resolution for this PIA(Pain in the ASS) approach (for forms modules which do not use folder views) by using developer 6i (Uhu, beware Oracle fan boys would tell you, Oracle does not support developer 6i any further)
Create a template.fmb using Developer 6i forms
Change the system coordinates to use inches in the place of points
- Save the template.fmb
- Using save as, save your template.fmb as a new fmb file (eg: aa.fmb)
- Connect to apps database instance and start adding windows, canvases, blocks etc to the form and TEST IT locally!!!
- TEST it until the results are as expected.
- Make a backup for your working module (copy aa.fmb to bb.fmb for example)
Open your aa.fmb file, developed using forms 6i with Developer suite 10g forms designer (You will get prompts stating the possible conversions for triggers, coding etc)
Open TEMPLATE.fmb and save it as “MYAPPSFORM.fmb”
Now, please give maximum attention towards copying the objects from your 6i module which is opened with Developer 10g forms, TO your form module which will go to apps instance
- Copy all the windows you have created with 6i module to 10g forms
- Copy all the canvases you have created with 6i module to 10g forms
- Copy all the blocks you have created with 6i module to 10g forms
- Copy record groups, lovs, form level triggers if any
Now, try to compile the 10g form. If you have copied everything from 6i, this new form shouldn’t give you any compilation errors.
Move the form to apps instance, compile, create forms, menus and do final testing, confirming everything is working fine.