Hi,

This is way I setup VFP with TS.

1. install the app in c:\program files\appname
2. for each user I create a c:\username\temp directory.
3. in the login script include is line subst t: c:\username\temp
4. in c:\program files\appname\config.fpw set the temp sort etc to t:\ and delete foxuser from c:\program files\appname
This ensures that each user has a separate work space and foxuser.dbf
i.e.

tmpfiles = t:\
sortwork = t:\
progwork = t:\
editwork = t:\
resource=t:\foxuser.dbf

5. in the login script also add subst g: c:\appname\data and add the following to the appname.ini
[DataLocation]
Database = g:\appname\data

*** Note *** Subst only works on server local drives

The above setup gives the most stable and highest performance installation.

Hope this helps.


>Could you give a little more detail on this? I have a client running Process Pro (based on Accpac/SBT) and they run the app via TS even for the local users. They have the Z: drive mapped to the PPRO folder. You're saying it's better not to map a drive on the TS machine, but to use SUBST? That's not a command I ever used much and certainly not in quite awhile. Can you fill in some detail on this. Heck, I might just tell all my clients to run my apps via TS if I could take the redirector out of the equation. It seems to be an important factor in relation to some issues that sometimes pop up.
>
>Russell Campbell
>
>>Hi,
>>TS will always be faster than access via the network, especially if you use SUBST to point to the data, as it takes the redirector out of the equation. i.e. the Database engine has access to the full bus bandwith of the server for access, where as the local workstations have something less than 70Mb/sec/No. Workstations accessing at that time, under high load this can be lower than 5Mb/Sec.
>>
>>Mapping a drive to the dataset on the TS will have measureable performance degradation.
>>
>>UPDATED: A 1Gb link from the Switch to the server does reduce to server bottleneck somewhat.
>>
>>Also where does the exe reside on the client or the server.
>>