Try OpenEdge Now
skip to main content
WebClient Applications
Overview : Differences between WebClient and the standard ABL client
 

Differences between WebClient and the standard ABL client

The following table compares WebClient and the standard ABL client.
Table 1. Comparing WebClient to the standard ABL client
Feature
WebClient
Standard ABL client
Execution
Contains no compiler; runs as a reduced-size executable.
Compiles source and runs as a complete ABL client executable.
Data access
Supports temp-table access, but does not support direct access to the OpenEdge® database or DataServers; 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 ABL 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 ABL 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 ABL client on the end user's behalf.The ABL procedures that the application comprises must be installed on the end user's machine prior to run time.