>Elmer,
>
>I guess this is the crux:
>
>---------
>One customer has asked about TS to prevent them from having to update multiple computers when the exe's are updated (not that often BTW), and to allow the app to work faster than running the EXE over the network.
>-----------
>
>If this is the reason for TS, I'm kind of wondering why they think TS will be faster.
>
>If I'm following this right, this particular client is experiencing speed problems but they don't want to allow their users to install locally to solve the speed problems. They want the control of centralization.
>
>If their network setup is causing performance problems, I don't think it is going to necessarily get *better* because of TS. Your app is configurable as far as where it puts things, so maybe they've just configured it to put things in an inefficient place <s>?
>
>When they run the application under TS the tempfiles are going to go somewhere on the network, just as they do in the "control freak" cases now <s>. The question will still be "where and how well configured".
>
>>L<
Actually this was requested by a new client who has not even installed the software. I think that they were anticipating that it might be a hassle to have to update each workstation when client files need to be updated like when adding a report or the occasional bug fix. I think that I can convince them that the loader can make this an automated thing.

The control freaks that have it installed on the network and don't allow anything installed or saved locally have been using the program for over a year without a problem except for users complaining of the delay that they see when it launcches a form or prints reports. (They also complain about every other application that they have to use on a daily basis since they all are sluggish.) It is not really that excessive, mainly on large reports when it is querying a large amount of data before printing, but if you are used to a screen popping up as soon as you release the mouse click or having subsecond queries, it is noticably slow responding. It takes perhaps a 2 or 3 seconds to launch the largest data entry screen but navigates between records pretty snappy and saving records from this screen may take a second or two while it validates changes and updates monitoring schedules. Fortunately they are using SQL Server and I am pulling down only the required records using parameterized views and SPT. It is just not as fast as it could be because of the way that they have it setup. The IT guys there are not dissatisfied and the users either don't complain too much to them or maybe they just don't hear the complaints like I do. The users there are of employees of my company on contract at the plant and they have worked at other plants using the software and see it working as it should.

I may experiment with TS with this new client to see how it will perform and if there would be any problems associated with com port redirection and the daily serial communication between the data collection devices. It probably won't be until after the first of the year before I get back to this so I may have other questions when I get more into it. If you have any links to resources about TS and the com port redirection, I would appreciate it if you could post them here.

Thanks for your help and Happy Thanksgiving.