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 Database or DataServer access; relies on a connected AppServer to provide indirect access to all databases and DataServers.
|
Supports direct access to all Progress data objects, as well as indirect access to databases and DataServers using a connected AppServer.
|
Customization
|
Cannot be customized using PROBUILD.
|
Can be customized using PROBUILD.
|
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 comprise the application 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 comprise the application must be installed on the end user’s machine prior to run time.
|