We are running our fpw26 app over a network, with a file server about 20 miles away. Frequently, performance suffers because of bandwidth constraints, since all record selection and data processing must be done by workstations on data that is sent from the file server.

We are invesigating running our app on a terminal server, which would allow all record selection to be done locally. The terminal server would be functioning not only as a file server but also as a workstation, and the only thing that would go over the network to our users would be screen images and their responding keyboarding and mouse manipulations. It should be powerful enough to support multiple user logins and fpw26 sessions (each with its own temp directory and memory space.)

However, there is a problem. If two sessions do certain things at the same time, the server comes to a virtual standstill. For example, inserting 100000 copies of a record into a table takes just under 2 minutes, just under 1000 inserts/second. But if two sessions are doing this, the speed for both drops to about 1 record every other second, with spurts of 10 or 20 records evey few seconds. By moving the temporary directories to another disk or cutting back on memory usage (!), I can get the speed up to about 45 records a second.

Does anybody have any relevant experience with fpw26 and ms terminal server?

Thanks
--Dave