Document-ID: 34335.1
Subject: Running Forms 4.0 & 4.5 from same /Orawin directory ( PC )
Author: RCTAYLOR
Last Modified: 28 May 96
Coexistence of CDE1 and CDE2
What is CDE1?
CDE1 consists mainly of the following products:
Oracle Forms - 4.0.x.x
Oracle Reports - 2.0.x.x
Oracle Graphics - 2.0.x.x
Oracle Data Browser - 1.0.x.x
Oracle SQL*Plus - 3.1.x.x
Oracle Book - 2.0.x.x
What is CDE2?
CDE2 consists mainly of the following products:
Oracle Forms - 4.5.x.x
Oracle Reports - 2.5.x.x
Oracle Graphics - 2.5.x.x
Oracle Data Browser - 2.0.x.x
Oracle SQL*Plus - 3.1.x.x
Oracle Book - 2.1.x.x
Oracle Book SGML Designer - 2.1.x.x
Oracle Procedure Builder - 1.5.x.x
Note: CDE2 is currently available only on the MS-Windows platform. Most of
the discussion in this bulletin is therefore directed towards the
MS-Windows platform.
The ORACLE HOME directory for the CDE software will be referred to as
the ORAWIN directory.
Oracle Corporation fully supports the installation of CDE on Novell
Netware LANs. It is okay to have the ORAWIN directory on a Novell File
Server. While other LAN environments (Windows NT, PC-NFS) will probably
work, Oracle Corporation does not support such environments at this
time.
Why would I want CDE1 and CDE2 at the same time?
- CDE2 is currently "Production" only on the MS-Windows platform. If your
site is multi-platform (the same applications are running on multiple
operating systems), you are restricted to CDE1 at this time. You may
want to continue using existing applications based on CDE1 and
begin future development in CDE2 to take advantage of new features.
- Additional functionality such as OLE and VBX support is available with
CDE2.
- Improved "look and feel" of CDE2.
Can CDE1 and CDE2 coexist on the same filesystem?
YES, it is perfectly okay to install CDE1 and CDE2 in the same ORAWIN
directory. There will not be any conflicts with Dynamic Link Libraries (DLLs)
between the products. There is also no conflict with message files, resource
files and any other internal files. Separate parameters are provided in
the configuration file (the ORACLE.INI on MS-Windows). All the executable
names are also different. The products from CDE1 and CDE2 will install into
separate sub-directories.
For example, Oracle Forms 4.0. will install in a directory called FORMS40
and Oracle Forms 4.5 will install in a directory called FORMS45. All the
message files, resource files and other internal files will go into their
respective directories. The executable names are F40DES.EXE and F45DES.EXE.
But wait, I was told in the past that different versions could not coexist?
This is partially true in only two situations.
- Two version of CDE1 cannot be installed into the same File System. For
example, it is not a good idea to install Oracle Forms 4.0.12 and Oracle
Forms 4.0.13 into the same ORAWIN directory. In general, we do not
recommend that you install two releases of CDE1 (or CDE2) into the same
ORAWIN directory. However, it is okay to install ONE set of CDE1
and ONE set of CDE2 into the same ORAWIN directory.
- During the BETA cycle for CDE2 there was a conflict with certain files
between Production CDE1 and Beta CDE2 software. This conflict does not
effect production CDE2 software.
How about the Database Tables?
There is NO conflict in any datbase tables required for CDE1 and CDE2. The
tables for CDE1 and CDE2 can be created on the same instance of ORACLE.
There are two broad set of tables required in the database in order to save
CDE1 and CDE2 modules to the database. These can be classified as:
- Tools Utilities Database Tables.
The Tools Utilities Database tables are shared by CDE1 and CDE2. You
need to run the SQL scripts to create these tables once for all CDE
products. If you already have a CDE1 installation and have created
all the Tools Utilities Database tables, you should not run these
scripts for CDE2.
- Product tables.
In general, there is a separate SQL script to create the tables required
for each CDE tool. Every product uses a separate table to save its
modules. The same product from CDE1 and CDE2 are treated as separate
products and will have separate tables in the database. For example,
Oracle Forms 4.0 and Oracle Forms 4.5 will use different tables to
save their modules. Therefore, there is no conflict in the database
objects for these products.
Can I run applications created in CDE1 in CDE2?
Generally speaking, this is possible. However you do need to regenerate your
CDE1 applications in CDE2. It is best to look up the documentation for the
CDE product in question.
For example, a .FMB file from Oracle Forms 4.0 can be read by the Oracle
Forms 4.5 designer, but in order to run the application under Oracle Forms
4.5, you will have to create an .FMX under Forms 4.5.
How about the reverse, can I take a CDE2 application and run under CDE1?
This should not be attempted, except under extreme conditions. Should you
need to do this, it may be possible with some additional work. You should
look up the documentation for your CDE product to get exact details before
attempting such a move.
For example, according to section 11.14 of the Oracle Forms release notes,
there is no backward compatibility. However, Oracle Reports does provide
a R25CONV utility for this purpose.
Can I use CDE1 modules stored in the database in CDE2?
Yes, you can use modules from CDE1 in CDE2 applications. However, you need
to save them in the corresponding CDE2 table. For example, if you have a
Form module saved in the database from Oracle Forms 4.0, you will need to
bring the .FMB file for this module into the Oracle Forms 4.5 designer and
save it to the database from here before using it in Forms 4.5.
How about the configuration file?
The configuration file (ORACLE.INI on the MS-Windows platform) can be shared
by CDE1 and CDE2. There is no conflict between any parameters used by CDE1
and CDE2.
What about SQL*NET?
SQL*NET is always independent of the front-end CDE application or the
database. The same SQL*NET can be used by both CDE1 and CDE2 applications.
In general, you should always use the latest release of SQL*NET available.