>My Reservation System works with good speed at the customers main office. Likewise, it works with good speed at one of their out of town offices, connected via a 128K frame relay on local phone lines. However when both the main office and the out of town office connect, there is a huge degradation in the system in both offices. So much so that it takes from 10 to 20 minutes for some forms to load that normally take just seconds or fractions thereof.
>
>The server in the main office is running Windows NT.
>
>Last year they were running Novell on the network and things appeared to be fine, but they didn't have both offices accessing the app at the same time, so I don't know if this is the problem.
>
>I hope someone can shed some light on this for me, and possibly some solutions.
>

Is the executable on the server or on each workstation? I've found that installing the executable on each workstation, and locating the temporary files locally, will show a major improvement in application responsiveness when running in a shared environment; using a launcher that checks the network to see if a new version of the executable is there, and if so copying it to the local system, and then launching the local copy, also makes deploying changes much easier; the network is updated, and each workstation copies the new version to itself at it's next opportunity.