Wrong code being executed in 10g

Question

Hi all,
I'm having a problem where my form is picking up the wrong source code.
I have formA which calls formB. FormA and formB both have an application library attached with common code. In the pre-form trigger of both forms they call a procedure eaq$event_form which in turn calls a procedure ma$pre_form. These procedures are both contained in the application_library and a local copy of ma$pre_form which does something other than the generic code is placed in formA (but not formB).
When the forms are run, the local copy of ma$pre_form in formA fires instead of the application_library version which is what I want, but when formA calls formB using call_form(formB,NO_HIDE,DO_REPLACE,NO_QUERY_ONLY,NO_SHARE_LIBRARY_DATA), formB's pre-form trigger fires and picks up the application library version of eaq$event_form, but then picks up formA's version of ma$pre_form instead of the application library version! How can this be???
Incidentally if I call ma$pre_form directly from formB in the pre-form trigger it picks up the application library version correctly, but indirectly calling it via eaq$event_form does not work (even if I put a local copy of the procedure in formB!)
Now this all works in client server as I'd expect, but since migrating to 10g it doesn't.
Does anyone have any ideas?

Answer 1

Hi,
Sorry for the late reply, but I was off for the Holidays. Anyway.
I have tested your scenario step by step. and it works just the way you're saying.
But, what's happening here is just as Steve have mentioned in his second post.
<quote>All the codes are in the same "bucket"</quote>
And as I mentioned in my first post the local unit precedes the library, and that's why you are seeing the message from the local unit.
I changed the name of the local unit from MY_PRE_FROM to MY_PRE_FORM_LOCAL, and it worked just fine with me.
I suggest you try it, it should work.
So when we run formA we should see the following messages
'in generic call'
'in formA local'
Here what you are seeing the the precedences of the local unit over the library unit whenever they share the same name.
but logically you should see the library code MY_GENERIC_CALL being executed and showing a message of
PROCEDURE MY_GENERIC_CALL IS
BEGIN
     message('in generic call');
     my_pre_form;
END;and in turn calling to MY_PRE_FORM and the latter shows the message
PROCEDURE my_pre_form IS
BEGIN
message('in lib my pre-form');
END;so you should see:
in generic call
in lib my pre-form
and what's happening with you is the local unit is being preceded from forma over the library unit. As if you are calling the local unit from the library. or at least this is what seems to be happening.
Changing the local unit's name is making the difference.
Regards,
Tony Garabedian