Release 10.1A: OpenEdge Deployment:
WebClient Applications

> ## Differences between WebClient and the standard 4GL client

> Table 1–1 compares WebClient and the standard Progress 4GL client.

> Table 1–1: Comparing WebClient to the standard 4GL client
> Feature | WebClient | Standard 4GL client
> --- | --- | ---
> Execution | Contains no compiler; runs as a reduced-size executable. | Can compile source and runs as a complete 4GL client executable.
> Data access | Supports temp-table access, but does not support direct Progress OpenEdgeŽ Database or DataServer access; relies on a connected AppServer™ to provide indirect access to all databases and DataServers. | Supports direct access to all data objects, as well as indirect access to databases and DataServers using a connected AppServer.
> Customization | Cannot be customized using OEBuild. | Can be customized using OEBuild.
> User interface | Supports only the graphical user interface (GUI) and batch modes in Windows. | Supports all 4GL user-interface modes.
> Method of launch | Is typically launched by accessing a Web page or a shortcut that runs the WebClient Initializer, which performs certain housekeeping tasks and automatically executes WebClient on the end user’s behalf. The 4GL procedures that the application comprises do not have to be installed on the end user’s machine prior to run time. | Is typically launched by executing a script or shortcut you provide that executes the 4GL client on the end user’s behalf. The 4GL procedures that the application comprises must be installed on the end user’s machine prior to run time.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095