Limitations in Thin Client Environments

Note that there are some limitations to running a program with thin client. You may need to make some adjustments to your program if you rely on these features:

• The SCREEN EDITED-UPDATES=Formatted runtime configuration variable is not supported. Generally speaking, you can continue to run programs that use this feature without changing them. The user will experience a formatting difference while entering data, but the final result should be the same.
• Creating a graphical component does not move the cursor to the cell to the component's right. This restriction does not affect relative graphical component placement in the Screen Section (for example, "col + 2").
• The grid control does not generate the MSG-CELL-GOTO-DRAG event. This is done for performance reasons. Because of this, you cannot use the REGION-COLOR property to highlight an area when the mouse is dragged over it. See Grid Control for a description of an alternate technique for doing this.
• The runtime assumes that graphical components and windows are successfully created in the thin client. If the client runs out of memory, the creation succeeds, but subsequent operation is undefined.
• The CREATE statement can create only COM and .NET objects on Windows-based servers. See CREATE Statement in the ACUCOBOL-GT Reference Manual for more information.
• The JUSTIFY_NUM_FIELDS configuration variable is not communicated to the thin client.
• The C$SETVARIANT library routine and OLE SAFEARRAY data type are supported in thin client environments, regardless of the kind of operating system on the server. The C$GETVARIANT library routine, however, is not supported and returns a negative RESULT-CODE value in thin client environments. To learn more about the C$SETVARIANT routine, refer to the appendix "Library Routines" in ACUCOBOL-GT Appendices.
  Note: You should be careful when using C$SETVARIANT in thin client environments, because it generates network traffic and can affect performance. When using this library routine in a thin client environment, you should pass only small amounts of data.
• The WIN32_CTL_INPUT_STATUS configuration variable, which affects ACCEPT FROM INPUT STATUS behavior, is not supported in a thin client environment.
• The thin client environment provides limited support for the SHARED_LIBRARY_LIST configuration variable and the "-y" runtime option. Note that they do not load client-side dynamic link libraries (DLLs) for thin client applications that make calls using the CALL verb "@[DISPLAY]:" syntax. These applications must explicitly load the DLL by calling it with the CALL verb before calling a function within the DLL. For more information about SHARED_LIBRARY_LIST, refer to the appendix "Configuration Variables" in ACUCOBOL-GT Appendices. See Compiler and Runtime in the ACUCOBOL-GT User’s Guide to learn more about the “-y” option.