AcuToWeb has certain limitations as to what your applications can contain, or on which platforms they can be deployed.
AcuToWeb has the following limitations or known issues:
Using CREATE to instantiate a client-side .NET assembly that contains no UI is not currently supported. The CREATE syntax
provides server-side execution using the
SERVER-NAME "Local:the_server_name" syntax.
AcuToWeb does not support AcuConnect encryption or compression. If one or both of those features are in use they must be deactivated.
If you need this functionality, use the AcuToWeb Gateway, which provides
gzip (native http/WebSocket compression, native http/websocket compression, turned on by default) and SSL (https/wss).
Editing a Gateway Service for details on how to configure SSL connections. SSL is usually needed for connections over a public network, and in such
circumstances, it is recommended to have the AcuToWeb Gateway behind a full-flagged web server such as Apache or IIS; see
Working with IIS or Apache.
- The AcuToWeb control panel only shows 32-bit AcuConnect services; it will not show 64-bit services. However, as long as the
64-bit AcuConnect service is running, you can still use the AcuToWeb functionality as normal.
- Character screen applications that use double-byte characters may experience some layout differences when running through
AcuToWeb as opposed to the standard runtime. You can mitigate against these differences by using
DBCS_fixed_table.css when running the application; see
Preparing Your Application.
- If you are running the AcuToWeb Gateway from the command line (see
Starting and Stopping a Gateway Service), and receive a 'side-by-side' error, you need to install the
MS Visual c++ 2008 Redistributable package. (note: it must be the base package, and not a subsequent service pack.)
- When using the Browser control, you cannot load any web pages that have not been coded to run within a frame. Also, due to
an in-built security feature in the iFrame element, you are unable to retrieve any of its information (such as the title)
if the source has a different document domain to the one that AcuToWeb is running in.
- If your application uses a non-default font, and you have inconsistencies between the font sizing in the AcuToWeb application
and the application when run through AcuThin, then you must use the AcuToWeb Desktop with your AcuToWeb application, to allow
the font rendering to be handled within extend.