Webutil-Problem (not the usual "PRE-FORM", "WHEN-NEW-FORM-INSTANCE" etc.)

Question

Hello,
We have an application with lots of modules, where we use webutil to create text files on the client for data exports. The export is called in a WHEN-BUTTON-PRESSED Trigger and usually works fine, but we have the following problem:
If two modules, where webutil is used, are opened at the same time and one module is closed, webutil does not function anymore in the other module. If we then try to create a text file after closing on module, we get the following error-message:
Oracle.forms.webutil.file.FileFunctions bean not found.
WEBUTIL.FILE.FILE_SELECTION_DIALOG_INT will not work.
It’s not only the FileFunctions bean, all other webutil functions do not work also anymore in the remaining module.
This is not the usual “PRE-FORM”, “WHEN-NEW-FORM-INSTANCE” etc. Webutil-Problem.
As I said before, webutil works, but when we close one module with webutil used, it does not work in another open module anymore.
Any Idea, why this happens and how to solve the problem???
Kind regards
Udo

Answer 1

Hello,
Yes, both modules work in the the same session and session is not disconnected, when one of the modules is closed.
Webutill.pll is attached on both forms and all forms in our application using webutil usually work fine with the exception mentioned above.
It's a bit difficult to explain, what happens in our application, but I try:
Our application consists of modules that call other modules with call_form or go_form , when the module is open, all in the same session. "Global" Parameters are passed with SHARE_LIBRARY_DATA. Usually the calling forms stays open.
In the following constellation webutil does not work anymore at a certain point :
- Open module A (with webutil attached) and webutil works
- Then module A calls module B (with webutil attached) and webutil works in module B
- GO_FORM (module A) and webutil still works (while module B is still open)
- CALL_FORM (module C) (in our case webutil is not attached to this module, but I think that is not the problem) module C closes module B (while module A stays open)
- After making a choice in module C, module C closes itself with EXIT_FORM.
- Go back to the open module A, make a new query with the choice made in module C and webutil does not work anymore in module A
Regards
Udo