AFAIK, VFP doesn't use 'the App Path registry key', whatever it is. You can use FileMon and RegMon utilites to see what's going on when VFP application loads. See http://fox.wikis.com/wc.dll?Wiki~RegMon and http://fox.wikis.com/wc.dll?Wiki~FilegMon

>Why doesn't my FoxPro 9.0 application honor the App Path Registry Key?
>My understanding is that the DLL path (runtime DLL's) follow this sequence:
>
>

>*1-The directories listed in the App Path registry key
>*2-The directory where the executable module for the current process is located.
>*3-The current directory.
>*4-The Windows system directory.
>*5-The Windows directory.
>*6-The directories listed in the PATH environment variable.
>
>

>
>The issue is that we have the runtime files in a shared folder to allow an unconfigured workstation to load the application and wish the workstations to copy the runtime libraries local (to imporve performance) after they are initially run. The workstations copy the files local and create the app path registry entry for the application name (exe name) with a default and path entry, but the workstations still load the runtime DLL's from the share (2).
>
>These are XP and 2003 workstations. Some or 2000. But the issue is across the board.