There is a migration assistant frmplsqlconv.bat in your 12c install. If you have only a few few forms, then you can open them manually.
I don't know what 10 applications means. Is that 10 forms or you have 10 application that use an unknown number of forms?
Thanks for your respond.
I have 20 different modules which are irrelevant with each other.
If it is just 20 .fmb files, I would open them one at a time in 12c and recompile. 12c will open 6i .fmb file. You can still use the migration assistant though.
Migration assistant is painless and will convert your code properly.
Upgrading 20 modules would/should be fairly simple even if they are unrelated. However, I strongly recommend you review the Forms 6i to 12c Upgrade Guide before beginning.
As Gary mentioned, FMA (Forms Migration Assistant) can be used, but time and skill permitting, I recommend making changes manually if possible.
1 person found this helpful
It can be hard - it can be easy. But client/server to 3tier is a gamechange.
All Client Logic i/o to the operating system has to be replaced with webutil.
I had a couple of these projects and it does not depend on the number of modules.
In one project with 120 forms and 60 reports it took 10 days.
In another one with 60 Forms four month.
It is a question of complexity, references and used logic and APIs like OLE, Reports, WIN_API, ORAFFI. If you use these technics I would not do it nanually.
On my Demo Server you see an example how you can migrate with a Forms 22.214.171.124 module and Forms-API Master in Batch Mode from 6i to 126.96.36.199 in a couple of minutes.
All results are visible as logs. Check demo8 on
Friedhold Matz did the nice integration work to run alle Code changes in a silent mode.
You see a Minimum Forms6i Version there. With this Version you can do a one step migration.
Hi Frank. Thank you helping me
I just needs to know in oracle Middleware fusion does it come with inbuild Migration Assistant Tool or otherwise we need to install separately from oracle forms installation link.