>>Hi Richard,
>>
>>The TMPFILES, etc. should point to a directory on the C: drive. However, I'd make sure that the specified CONFIG.FPW file was the one actually in use. If, for example, the DOS environment variable FOXPROWCFG is pointing to a different configuration file (other than in the default directory), and you're assuming that the one in the default directory is being used, any changes in that (in the default directory) file will have no effect.
>
>George:
>I think we've cracked it. By putting a copy of the executable on the workstation and also the ESL file together with a CONFIG.FPW path pointing back to the Server's Data Directory, we can now do the processing in about 2 or 3 times the time taken when running on the server. This is directly proportional to the relative processor's speeds.
>
>Not sure if this is a valid solution, but it sure as heck works like a dream.
>
>Thanks for your input which triggered the "old grey cells"
>
Richard,

You're welcome. I think that it is a valid solution. All things being equal (which they rarely are< g >), a local executable should always outperform one on the server. Naturally, to what degree is dependant on a number of issue.

Glad to be of help.