I have heard that sentence so many times.
It should be rephrased to "Oracle want their customers to let Oracle Forms built applications to fade away". The reason for that is the there are new things, jDeveloper and other products that are in the pipe line to be sold.
However, there are very many business critical systems out here - in Sweden as well as in the world - that uses a stable, in production running Oracle Forms/Reports/Discoverer-application. The important thing here is business critical, and stable. Such applications are not taken out of service in an afternoon without a controlled, in-depth study on the cricital businesses processes that are supported by this application.
Slowly fades away is an understatement. The Oracle Forms/Reports/Discoverer-applications has always been fading away, let's say in 5-8 years or so. And believe me, when I say that there are many many applications in critical production systems that will be around for at least 5-8 years more.
There is a natural fear to exchange horses in the middle of the stream.
My advice is to isolate parts of existing Oracle F/R/D-applications and investigate what path to take, are you going to JDeveloper, Application Express or a mix of them both, or are you going to slowly move to JDeveloper, ApplicationExpress or Open Source-solutions? Or are you going to .net-thread?
The technical part of the matter is just the underlying part, the important thing is to get in place a technical platform for all your business applications, a standard to build applications upon.
10g (1) 11c (1) 11g (5) 12c (4) 3.0 (1) ApEx (4) Cloud (11) database (10) DBA (1) EBR (1) EC2 (2) education (3) EOUC (1) ExaData (1) F2F (1) Forms (7) java (1) language (2) memorabilia (2) Metalink vs MOS (4) multi-cultural (4) on-line communities (1) oracle (7) performance (5) projects (1) reciproke (1) Reports (2) RUP (1) sales (2) services (5) silence (1) SOA (3) SQL Server (3) standards (6) Sun (1) support (6) W8 (1) WebLogic Server (5)