>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?

You could always compile before executing the prg, to be sure you have always the latest version. Maybe implement a manager that compiles all necessary prgs on startup, so you don't do it unnecessarily often.