Tools - Forms Dependency Checker

This page provides information about the tool Forms Dependency Checker (CASTFormsDependencyCheckerGUI.jar) which points out the FMBs which are the part of dependency cycle circuits.

Dependency cycle circuit : If one .fmb (say A) is calling other .fmb (say B) and which is calling .fmb (say C), which is calling first .fmb (i.e. A), then this is called Dependency cycle circuit.

This tool can be used, if during the Oracle Forms extraction, there is no fatal error and extraction finishes without fatal error, but with zero extraction, which suggest there may be dependency cycle.

If Oracle Forms extraction finishes without fatal error, but with zero extraction, this suggest there may be dependency cycle. So this tool can be used to identify the fmbs which are in cycle and identified fmbs can be excluded from extraction for successful extraction.

This section is not applicable for this page.

1. Download the tool CASTFormsDependencyCheckerGUI.zip
2. Unzip and double click on the jar (CASTFormsDependencyCheckerGUI.jar) to launch tool as shown below.
   
   
3. Click on the "View" menu and select "Advance mode"
4. Select the Forms source in "Forms Root path" in General tab as pointed in above screenshot.
5. Click on the Advance tab and select log path in "Log file" as pointed in below screenshot.
   
6. Click on "Run Application"
7. Once it is finished, open log and notice the fmbs which are in dependency cycle.
8. This will be listed under "New cycle detected", example as shown below
   
   In the above example following fmbs are in cycle:

XXXX.fmb
XXXX_pan_as_act.fmb
XXXX_pan_as_doc.fmb
XXXX_pan_rem_me.fmb
XXXX_pan_as_note.fmb
XXXX_pan_my_act.fmb
XXXX_pan_as_inc.fmb
XXXX_pan_jump_go.fmb

This tool can be used before packaging your Forms application in order to check if there is any dependency circle between fmb files.