Probably you may consider the different scenario where the VFP run libraries installation is not required. As far as I understand, you somehow have Visual FoxPro application exe file in the directory. Probably you just copy it there (which is not recommended as the clean way is to install application, not to copy it).

However, you may do the very same with VFP dlls: instead of installing VFP run dlls, just put them into the directory along with your exe file.



>Hello,
>
>I have an application in FoxPro 2.6 (Windows) that launches an executable in Visual FoxPro:
>

! /N PreviewForm.exe

>Now this would cause an error if the VFP libraries are not installed on that computer.
>Instead it would be nice to display a message that the user needs to install those libraries before using this functionality.
>
>But how can I find out from FoxPro 2.6 whether the VFP9 libraries are installed?
>
>My guess would be to use RegFN and CallFn, using a 16 bit dll, but I am not at all familiar with 16bit dlls.