Team Developer in a Citrix or Terminal Server Environment

From Support Wiki

Jump to: navigation, search
Team Developer in a Citrix or Terminal Server Environment

*Updated April 4, 2003 by Alessa Tuppein

Description:
Team Developer is not supported running on either a Citrix or a Terminal Server Environment.

With this in mind, for your reference, we have provided some reported issues that may be run into when using these environments along with some solutions.

Known Issues:
Citrix WinFrame (version 1.7 and 1.8 emulate a Windows NT 3.5.1 environment.
Team Developer 1.5 and CTD 2.0 and greater are certified with Windows NT version 4 (or later). So, these versions will NOT work on Citrix WinFrame.

Citrix Metaframe 1.8 can emulate a Windows NT4 or Windows 2000 environment.
However, GUPTA has not tested and has not certified any CTD application to run under this environment. This is recorded under the Centura enhancement requests 71705 and 73265

Team Developer is not "Terminal Server aware." What this means is that Team Developer does not use the individual user heap. Team Developer draws from the standard heap and assumes there is only one heap to draw from. In the case of multiple users, Team Developer is still going to only use the standard heap.

Team Developer will also not be aware of multiple users using a Terminal Server machine and will use the standard area to save files. Temporary files will not be placed under individual user areas as Team Developer cannot detect individual users' settings i.e. My Documents for individual users.

Problem:
Images in a Team Developer application may appear to "flicker".

Solution:
This can be resolved by reducing the resolution of the embedded images.
Make sure you use the standard palette for all your colors.

Problem:
Applications may show the error "There are not enough resources available to open this form."

Solution:
This is caused by a design limitation in Windows. Try to run fewer applications simultaneously. Also, in the application, reduce the number of window objects to be administered at one time. You can try the following:

    * Change the application window design to show less data fields simultaneously.
    * Make certain you close windows that you don't need.
    * Restrict the user from opening too many windows.