Migrating forms to 11g - problems with absolete built-ins

Question

Sorry if it's the wrong section, but nerves are kicking in and I'm lost.
I've been trying to migrate an old, probably 8i database with its tools and forms into 11g. All software seems to run fine, but when I try to run the forms I either get "this form was made using an old forms builder" error, or worse - some enigmatic FRM and ORA (exception 6508) errors apparently connected to lack of some procedure called in the form triggers.
Now you'd probably say "just recompile those forms". But I can't - I get tons of compilation errors, mostly comming in from absolete built-ins or trying to select from system views. That happens when trying to recompile libraries referenced by those forms, which is probably why i get those procedure lacking errors.
Since the ammount and nature of those overwhelmed me I tried using Forms Migration Assistant...talk about betting on the wrong horse. First I had to change the 'start in' property of the assitants shortcut to where i stored the forms/libraries or else it kept throwing the libs out of said forms. Then I got a bundle of pld files and the most important libraries unchanged, with no mention of any problem in the assistants log. Needless to say my forms still get those procedure lack errors.
I'm pretty sure I can somehow handle correcting the forms if the libraries were ok, but I just can't cope with those problems:
-what to do about system view selects in triggers and library procedures? The compiler just treats them as unknown identifiers. I had the same problem elsewhere and it was about privileges, but this time I can't identify the user from whom those privs are read (in fact, isn't it whoever is using the form at the time?) so far I've noticed it try to use dba_users and dba_roles
-what to do to correct a library (which can have dependencies on other libraries) to be compatible or at least compile'able with the new Forms Builder without spending a year on it all?
I've tried applying changes mentionned in the assistants log (like changing RUN_PRODUCT calls to RP2RRO.RP2RRO_RUN_PRODUCT), but it didn't do any good

Answer 1

Well for me the forms were ok to open with 11g, just had to correct differences and recompile to run.
That there script is a ton of help!..well you forgot to mention the Output_File parameter, but I could find that myself now that I knew what to look at. Now if I could also set it not to produce .err files when everything went fine and to set the output names so that the old compiled forms get overwritten..
the SRW.* calls turned out to be things used in Reports, so it was hopeless to compile in forms..but also not needed
as for ENABLE_ITEM and DISABLE_ITEM I found these to use as their definitions in a library, that proved sufficient.
procedure enable_item
( p_menuName in varchar2
, p_menuItemName in varchar2
) is
v_menuItem menuitem;
begin
v_menuItem := find_menu_item(p_menuName||'.'||
p_menuItemName);
if (not id_null(v_menuItem))
and (get_menu_item_property(v_menuItem,visible) = 'TRUE')
then
set_menu_item_property(v_menuItem, enabled, property_true);
end if;
end;
procedure disable_item
( p_menuName in varchar2
, p_menuItemName in varchar2
) is
v_menuItem menuitem;
begin
v_menuItem := find_menu_item(p_menuName||'.'||
p_menuItemName);
if (not id_null(v_menuItem))
and (get_menu_item_property(v_menuItem,visible) = 'TRUE')
then
set_menu_item_property(v_menuItem, enabled, property_false);
end if;
end;Some forms still playing with me, but the compilation issues there don't seem to be connected with this topic..and now I got issues with reports >.< but that requires a topic elsewhere. Thanks all!