>I have an app, recently rebuilt in VFP9 and packaged using InstallShield Express V5. It installs and runs fine on W98, W2K AND XP OS's - but NT4 generates the error "The procedure entry point GetLongPathNameA could not be located in the dynamic link library Kernel32.dll"
>I have found references on the web to the fact that GetLongPathName does not work under NT4 and suggestions to use an alternative API. However, I do not use GetLongPathName in my application. So I can't use an alternative! Where will the call to GetLongPathName be coming from, and how do I avoid it?
>
>( I do not know why the error message shows an "A" suffixed to GetLongPathName. Is this a clue?)

Barry,

VFP9 is not suppoerted under WinNT. The call to GetLongPathName comes from within VFP. See http://fox.wikis.com/wc.dll?Wiki~VFPSupportedOS for details and possible solution.

The GetLongPathNameA means that it's ASCII version of DLL and GetLongPathNameW - Unicode.