Search results

I agree with Tom. Note, if you have multiple versions of Progress installed on the same server, you will NOT want to define the typical Progress envrionmental variables and you should let the symix.ini and/or your custom script define the DLC variable to indicate which version of Progress you...

You would basically setup the terminal server exactly as if it were a "FAT" client. All code loaded locally, and dont take the default installation paths. (they are too long to type multiple times) Using something like x:\syteline and x:\dlc or x:\progress Jason jason @ tecpeople.net

You would basically setup the terminal server exactly as if it were a "FAT" client. All code loaded locally, and dont take the default installation paths. (they are too long to type multiple times) Using something like x:\syteline and x:\dlc or x:\progress

If your Syteline Printer Defaults are defined correctly with the UNC path to the printers, printing should work perfect. I would not recommend using "PRINTER" as the default printer name. This assumes that the client has a local default printer; and this works for most windows applications, but...