Because your going through the network, you NEED the hotfix for file read errors as you will get them with TS in this situation. The articles were meantioned earlier and with those fixes installed your problems should go away.

>Thanks for the info ... I never realized that Microsoft didn't recommend FPW2.6 on TS (we put this in a couple of years ago, maybe their "non-recommendation" came out after this).
>
>All this customer has is the Terminal Server running Windows 2000, about 6 Wyse thin clients, and 3 or 4 old PC's running Terminal Server Client. There are no other apps running in their TS sessions, all they use is this one FPW app. They haven't added any users since we installed the server, there are 8 users and I belive they have 512 Megs of ram. I was originally told that there should be 32 Megs per user, and we needed 256 for the OS, so that's why 512.
>
>As for disk caching, we'll have to check, I'm not sure of the setting.
>
>One other thing suggested by a network tech I know, was that we shouldn't map drives back to themselves. The data is physically stored in c:\pics\prodinv\livedata\. We mapped M: to c:\pics and use M:\prodinv\livedata as the path to the data. We also have separate user folders for temp files and indexes which are physically stored in c:\wwusers\username\ and we mapped Y: to c:\wwusers\username\. Then we put Y: in our config.fp file as follows:
>
>OVERLAY=Y:\ OVERWRITE
>EDITWORK=Y:\
>SORTWORK=Y:\
>PROGWORK=Y:\
>TMPFILES=Y:\
>
>Do you think that this mapping of a drive back to itself could cause in temporary disconnects of the app from it's data (which I assume is why we are getting the 1104's)?
>
>Thanks so much again for the info!
>
>Charles