>Network dude stepping in. The speed of the T1 line and protocol timeouts are the issue. The T1 link can experience spractic loads, which makes it a poor choice to run live data over. Most systems run distributed data, (client/server), and send updates over the link.
>
>You can up the timeout times for you IP or IPX protocols. A default IP timeout is 60 seconds, and IPX 30. You can change the IPX timeouts & # of retries in the 95 control panel under the protocol. I checked the IP, and you may have to hack an INI file.
>
>Contact your network support group. They should be able to tell you if the T1 link experiences burst modes where the link is maxed for more than the timeout (60 seconds) or is experiencing a large number of errors which result in a large amount of protocol transmission retries (WAN link problem, must use a protocol analyzer). If there are not any errors, and you have delays of over 60 seconds, your link is over loaded and should be upgraded. You should also consider how to migrate your app to client/server to alieviate traffic over the link.

Paul,

Thanks for the reply. I suspected it was most likely on the network side, but wanted to verify it. I have no control over the application since it is a commercial accounting system. I'm leaning toward a Thin Client solution to alleviate this, but their IS person (also heading up the project) wants "proof" that the application won't work over the T1. He also felt that it was a network timeout issue and that he should be able to increase the timeout and it would correct the problem. They don't have any problems with other applications (all client server based). I tried to tell him that he wasn't comparing apples for apples, but I don't think he gets it.

Again, I appreciate all of the replies. I will attempt to go back to him with some of this information so we can keep moving forward.