Like all Acucorp technologies, Acucorp's thin client solution can work alone or in conjunction with other technologies from the extendTM family of solutions.
If data will be stored on a separate data server in a three-tier architecture, your thin client solution can utilize AcuServer to provide transparent access to that data. The AcuAccess file established for AcuServer can be placed on the application server for use by AcuLaunch. If data will reside on the same server as the application, application runtime, and AcuLaunch, then AcuServer is not necessary because data access on the server is considered local.
If your application requires access to relational databases like Oracle, Informix, and Sybase, your thin client solution can utilize Acu4GLTM or AcuSQLTM technologies on the server to provide automatic data translation. The data can reside on the same server or a different server in this case.
When operating in a thin client configuration, you will rarely require distributed processing capabilities. If necessary, however, your thin client application can use AcuConnect, Acucorp's remote application server, to call another program on a second application server.
Acucorp's thin client solution plays an important role in the evolution of your application from old, green-screen terminal mode to modern graphical user interface capabilities. With our thin client solution, you can migrate your character-based application to ACUCOBOL-GT, display it on Windows hosts, and when you're ready, convert your screens to a full featured graphical user interface. You can develop your GUI in Windows using our graphical workbench, AcuBenchTM. You can even debug your remote server application from the workbench.
Talk to your Acucorp sales representative for help deciding which Acucorp technologies are right for you.