Mike,

The workstations have a drive mapped to a local NT server. I think this is a network problem (traffic, driver, configuration, hardware). It seems that when it hangs if they leave it long enough (30 minutes or more) it eventually comes back. The problem never occurs unless there is at least one other person in the application. It doesn't seem to matter what the other user(s) are doing in the application. The problem has occurred on all workstations. It almost seems like a table / record is not being handled correctly by the network and this is causing some sort of network contention.

Still investigating.....

>how are you accessing the data? \\theserver\drive\path sometimes doesn't work, especially if dial up networking is active! the network has to resolve the path and do the logins before you get your data.
>
>I've found that mapping the drive and forcing a reconnect at startup shows the network problems BEFORE my app is called, so the network guru gets the call, not me !! ( I do NOT use the mapping within the app, just use the mapping to show the network problem! )
>
>Also, be careful your app doesn't have any old (missing) COM servers included, that drove me up the wall once, the app searched forever, and since I was hiding all the dialog.......
>
>further also, be careful servers don't point back to the develpoment machine!