Printable View
Hi,
Please inform the steps involved in converting v2 style triggers to pl/SQL.
We do not have SQL*forms 3.0 installed in our dev environment, but have inp files with v2 style triggers.Planning to migrate them to 4.5 forms version. Is there away to convert V2 to pl/sql after migrating to 4.5 version.
thanks and regards
:confused:
Forms 4.5? V2? Are you implementing Y2K now?
hi Kris,
I am in the preocess of migrating 3.0 to 9i.If you can please help me on the v2 trigger conversion.
regards
hi
I do not have access to metalink.Anyways, I did a google search and came to know about the "V2-style to PL/SQL Forms Converter" in the URL http://www.orafaq.com/faqfrm3.htm#UPGRADE
They say that this package will read the SQL*Forms V3.0 tables and convert all V2-stype triggers to PL/SQL. Run it after you've upgraded from Forms V2.x or before you upgrade from Forms 3.0 to a higher release.
In my dev environment, I have the inp files,forms 4.5/6i/9i and 8.1.6/9i database.
I downloaded the above package and my database doesnot have any SQL*Forms table.what should I do in order to make the above converter work.I could not find any further details about the above converter.
thanks.
Problem Description:
Problem Description:
====================
Are Version 2.0 (V2) style triggers supported in Oracle Forms 4.X and 5.0?
Problem Explanation:
====================
How does the Forms upgrade process handle V2 style trigger conversions? Will
the V2 style triggers still work in Forms 4.X and 5.0, or will I have to
rewrite the code in PL/SQL?
Solution Description:
=====================
Third-party migration tools exist to convert SQL*Forms 3.0 to Oracle Forms,
including converting V2 style triggers to PL/SQL. Sierra Atlantic and Kumaran
Systems are part of the Oracle Open Tools Initiative (OTI), and have migration
tools available.
Sierra Atlantic
---------------
Sierrra Atlantic FormsGenie is an automated migration tool that will upgrade
SQL*Forms 3.0 applications to Developer/2000, and convert your V2 style
triggers to PL/SQL.
Web: http://www.SierraAtl.com
Email: FormsGenie@SierraAtl.com
Americas and Japan
------------------
Sierra Atlantic Inc.
830 Hillview Court, Suite 110
Milipitas, CA 95035 USA
Phone (408)956-3000
FAX (408) 956-3001
Europe, Middle East, Africa
---------------------------
Sierra Atlantic, UK
Phone 44-115-922-8600
FAX 44-115-922-5550
Asia-Pacific
------------
Sierra Optima Limited
Phone 91-40-3740-368, 3746122
FAX 91-40-3746419
Kumaran Systems
---------------
Kumaran Systems GUI*Converter is an automated migration tool that will upgrade
SQL*Forms 3.0 applications to Developer/2000. The Forms Converter will
convert your V2 style triggers to PL/SQL.
Web: http://www.kumaran.com
Worldwide Headquarters
Kumaran Systems, Inc.
701 Evans Avenue, Suite 509
Toronto, Ontario
Canada, M9C 1A3
Phone: 1-800-586-2726
(416) 626-1332 (Toronto)
United States Offices
12300 Twin Brooks Parkway, Suite 660
Rockville, Maryland
USA, 20852
Phone: 1-800-586-2726
Solution Explanation:
=====================
The Oracle Forms generator will not convert V2 style triggers to PL/SQL, but
there are third party products available that have this functionality.
See the "Oracle Open Tools Initiative" CD included with Developer/2000 for
more information on companies involved in the Oracle Open Tools Initiative.
V2 STYLE TRIGGERS RUN BUT ARE NOT CONVERTED TO PL/SQL
Solution Description:
=====================
If you convert a form that contains Version 2.0 style triggers, they will
still run in Developer/2000 Release 1.X and 2.0. You can view these triggers,
but you cannot edit or modify them.
The Oracle Forms Generator does not convert V2 style triggers into PL/SQL
triggers. During conversion, Oracle Forms copies the text of your triggers
verbatim. V2 style triggers remain V2 style triggers, and V3 style PL/SQL
triggers remain PL/SQL triggers.
If you want to edit the V2 style trigger, you must manually convert the
trigger to PL/SQL. There is no automatic mechanism to convert the V2 style
trigger to PL/SQL.
Some trigger names specific to SQL*Forms 2.3 / 3.0 are changed to Oracle Forms
nomenclature, but the TEXT of the triggers is NOT changed in any way. For
example, an On-Validate-Field trigger would be renamed to a When-Validate-Item
trigger, but the text of the trigger remains the same.
Solution Explanation:
=====================
SQL*Forms 2.3 used Version 2.0 style triggers, and did not use PL/SQL. V2
style trigger support is included only for backward compatibility with earlier
versions of Forms. All V2 style triggers should be converted to PL/SQL.
Thanks Kris for your continuous help.
We are not planning to go for any third party tools like kumaran / sierra and so we are going to migrate the forms on our own.
It is mentioned that v2 triggers has to be rewritten manually and cannot be converted automatically.
Can't I use the converter i mentioned in my previous reply.
regards