>Hi Folks,
>
>My little brother is a support tech. He had a call from a client today asking why users connecting to a Win2k Terminal Server were having problems running a FPD 2.6 exe. The details I know are as follows:
>
>1. FPD exe lives on a Win2k Member Server
>2. FPD Data lives on the same member server
>3. Terminal Server is another server in the domain
>4. LAN (multi)users are able to use the app just fine
>5. If there is > 1 user logged in via Terminal Server, when the first user disconnects, all remaining TS users get an "Error Reading File" and have to quit and restart.
>
>I guess my questions are:
>
>1. Has anyone run a FPD exe under Win2kTS?
>2. Is there any reason to believe that it might work?
>3. Has anyone got any (printable <g>) suggestions for making it work.
>

You have only 1 FOXUSER resource file; the first use grabs it exclusive, and everyone else dies. Four possible fixes:

(1) Put RESOURCE=OFF in CONFIG.FP - no one uses the FOXUSER file
(2) Flag FOXUSER.DBF and FOXUSER.FPT as Read-Only, so no one gets write access to it
(3) Assign a unique resource file per user via individual CONFIG files, use the DOS environment variable FOXPROCFG in the login script
(4) Put RESOURCE=OFF in CONFIG.FP; during your app startup, open FOXUSER.DBF and make a copy to a temporary file, and issue a SET RESOURCE TO temp file - the user gets a copy of the default FOXUSER settings, he can muck with it in his session til the cows come home, and you delete it when he exits.

If you store printer configs in FOXUSER, (2) or (4) are usually the best choices. If you don't use it, (1) is best. If everyone has their own unique settings, (3) is best.