My company uses a 16-bit application to access programs run on a Unix server. The application is published on a Metaframe 1.8 server farm with Windows NT 4.0 TSE and service pack 6. There is a latency in the screen update on workstations where a user can enter an entire screen of updates before the cursor moves on the terminal session. When the screen does refresh all changes can be seen. This is a problem as real-time response is required for some transactions. I have checked the network connection and reponse time on most of the workstations and the 16-bit application is the only one with latency. When running a full desktop with Run in separate memory space checked the latency disappears. I have not found a way to force published applications to use a separate memory space. Has anyone experienced this with published 16-bit applications or found a method to force use of separate memory space?