Oracle Forms is essentially a 4GL (highly stylized and abstract)
platform that has its applications designed from the database
structure down.
ASP.NET is essentially a 3GL that uses class
structures for its design base.
ASP.NET does have slick development
interfaces with Visual Studio and a rich GUI API that appears 4GL, but
it isn't.
Although Oracle PL/SQL is the greatest server-side stored procedure
language ever implemented, Oracle Forms attempts to use an older
version of it in a funky client-side engine, which will confuse the
hell out of you if you don't understand it incredibly well.
And last, but not least, Oracle Forms is at its core stateful - even
by browser - through a java applet.
ASP.NET is not stateful. This
alone should give you an idea of how much coding difference is
involved.
If you decide you must migrate, I'll quote you US$100/hour plus time
and materials to do the bulk of the the job. It is not a task for the
feint of heart. Contact me through my blog if you want to get
involved on a project together.
Michael O
http://blog.crisatunity.com
P.S. I've seen some of the automated Oracle Forms-to-JSP conversion
frameworks out there and it is conceivable that if your Forms2Net
program is similar and you have a massive amount of Forms (hundreds?)
you could use such a tool to get you 60% of the way, but that is a
best case scenario from what I've seen with Forms-to-JSP. But if you
have dozens of forms, automation would be counterproductive. Good
luck. You are facing some of the most miserable work you've ever
done.
> > > Anup- Hide quoted text -
>
> - Show quoted text -