Skip Headers

Oracle Forms Developer and OracleAS Forms Services Migrating Forms Applications from Forms 6i 10g (9.0.4) Part Number B10469-01 |
Home |  | Contents | Index

# 7
Changes to Client-Server Deployment and Forms Runtime

In order to streamline the tools available and simplify the development process for building Forms applications for the Web, client-server runtime is obsolete in Forms Developer and Forms Services, as it is not applicable to Web deployment.

If you currently deploy applications in a client-server environment and do not want to switch to Web-based deployment, you must remain on Forms 6i. When you use Forms Developer, part of the migration process is to upgrade your Forms applications for Web-based deployment.

See Chapter 15, "Migrating Client-Server Applications to the Web" for information about how client-server deployment differs from Web-based deployment.

## Effect on Forms Development

The obsolescence of client-server deployment will have little to no effect on the development and debugging of Forms applications. You can still run your code in Forms Developer without having to deploy on the Web first. Use the run-on-Web facility, which renders a true WYSIWYG representation of a Web-deployed form.

The PL/SQL debugger has been improved to allow debugging in a three-tier environment.

## Obsolete Forms Runtime Command Line Options

The following command line options for Runform have been removed because they relate to obsolete features:

- OptimizeSQL

- OptimizeTP

- Keyin

- Keyout

- Output_file

- Interactive

- Block_menu

- Statistics

## Obsolete Character Mode Runtime

Character mode runtime, which was only available on UNIX and VMS platforms, is no longer available. All character mode support has been removed from Forms Developer and Forms Services. See Chapter 6, "Properties" and Chapter 8, "Logical and GUI Attributes" for more information.

| Copyright © 2003, 2003 Oracle Corporation. All Rights Reserved. |
|  | Contents | Index