>Hi @all!
>
>In our VFP Application we offer our Customers Hooks so we/they can customize some behaviors.
>In the end these Hooks will be .prg Files in the subdir code.
>They are compiled, if they are not, and executed if needed.
>
>The complete Application is stored on an FileServer in network and every user starts the EXE there.
>
>Now, one Customer changed there Server's Hardware, which resulted in new UNC Paths.
>
>Since then our APP went slow.
>
>The Customer analyzed the Network traffic and he wondered why our APP still tries to access the Old UNC Path.
>Than he looked in the fxp and in the end of the File there where the "old" Paths stored.
>He Deleted the fxp's, our APP compiled them and now everything is fast.
>
>Bud:
>Why is the Path stored in the fxp?
>Can I prevent this behavior?

IIRC the bit where the full path the source files gets stored into the FXP, APP and EXE file was something that frequently caused headaches as far back as FoxPro DOS and FoxPro Windows. I do recall the headaches this caused (e.g. if your build directory was on the D: drive, then launching the application -- even if it now resided on a different drive like the F: drive, the D: drive -- often the CD-ROM drive would result). The "workaround" was often to perform the build on the C: drive and hope you never ran into a situation where C: wasn't a removable drive type.