We send you a confidentiality agreement, so that everything is in order.
You send us your *.fmb, *.pll, *.olb, *.mmb and *.rdf files, so that we can load all modules into the Oracle® Form Builder without errors. We do not need a database schema or data.
Each module is analyzed with several routines. These routines identify the following problem areas ...
... in Forms 6 migration:
- Client server mode objects (VBX, OLE, …)
- Build-ins dropped (break, pecs, …)
- Hardcoded names (call_form, run_report)
- Use of when-mouse-… events
- Use of timers and TabPages
- Case-sensitive names when using Unix application servers
- Incorrect PL/SQL name resolution
- Use of WebUtil (pll integration, referencing object group)
... in Forms 4.5 migration:
- Form build-ins with the same name as procedures and functions
- Declare cursor in triggers
- Conversion of boilerplate texts into prompts
- PL/SQL V1 after PL/SQL V8 conversion
- Replacement of the reference link database on file system
... in Forms 3 migration:
- Incompatibility of data type in form and in database
- Query Only fields in Insert or Update Statement
- Execution hierarchy for post-text-item-trigger (after)
- Conversion of the ‘Content Canvas’ into ‘Stacked Canvas’
- Enlargement of text fields for frames (bevel)
- Conversion from old to new build-in names (go_field -> go_item)
- Integration of the mouse navigation
Because the check routines are feely configurable, the jform Migration Check can also be extended immediately with regard to special features of your Oracle® Forms application.
We compile an individual offer with fixed prices, including timing.
