>>Why not, as an experiment? If that solves the problem... And the overhead of compiling is negligible nowadays. The code you have on the server, which checks for code change and compiles, can be moved to be executed on the workstations.

+1

Certainly you can overcome these sorts of path issues by judicious use of HOME and set path in the exe and/or supplying the full path when running the fxp.

Marco, other options to avoid extra complexity:

1) Move the prg rather than fxp to each workstation where compilation will be automatic when you run it. If you're worried about privacy of source code, distributing a standalone fxp is a few seconds of effort more secure than a prg.

- or - the way we used to do it:

2) Use FORCEPATH() to supply a fully pathed filename whenever you DO an external fxp. If you keep the url to the fxp location in a publicly accessible property or variable, it's easy enough.