- Differences between Open Client and PROIV Client

Differences between Open Client and PROIV Client

It is important to highlight the differences between the Open Client and PROIV Client:

Open Client requires no installation on your computer.
All application images are held in one place on the Open Client Server.
In Open Client, the vertical scrollbar automatically appears in multi-line edit boxes when the text does not fit in the view.
You cannot ‘shell out’ from Open Client.
The Kernel Prompt in the Open Client does not support the display of previous values.
DDE Poke is not supported in the Open Client.
Non-PROIV ActiveX controls must be re-implemented.
Open Client has no ‘client’ toolbar or menus. However, it does support application toolbars and menus.
Printing on your computer in Open Client is not automatic as it is in the PROIV Client. Printing is done by you saving or viewing a file, and then printing the file.
The Common Dialog ActiveX file picker is not available in Open Client, as direct access to your computer's hard drive is not permitted.
PROIV Function Keys can inadvertently control browser features, for example F1 displays a help page, F11 displays a full screen web page. Not all browsers allow this functionality to be turned off by a page script (i.e. Internet Explorer), and therefore some Function Keys may not work as expected in a PROIV Function. To help resolve this issue, Open Client has a built-in toolbar for the Function Keys that can be enabled by setting the Softkeys.enabled property in the Messages.properties file to TRUE. See Open Client Function Key Toolbar for more information.
Open Client does not support overlaid fields.
The PROIV Client does not support transparency in GIF images. However, the PROIV Open Client does support transparency.
The logic statements SYSTEM(“GUI …..") and SYSTEM-CRT are not supported in PROIV Open Client.
Open Client does not support the Javascript equivalents of dynamic ActiveX controls.
Open Client does not support the screen mapping feature - ENABLE(&#@SCRN-MAP)

Comment on this topic

Topic ID: 800027