>>>Just thought you would like to know, I found this out just today when I ran my code.
>>
>>Hi Brett,
>>
>>I don't know where this information came from, but I can't duplicate the results using either VFP 5.0 or 6.0 on Win 95 or 98. Because I had written about it in a recent Advisor article, I was interested in seeing if there was anything that I may have missed. Regardless of whether or not the file names have spaces, FindExecutable() worked just fine. Under VFP 5.0 on Win95, the file: C:\PROGRAM FILES\MAXIS\SIMCITY CLASSIC\README.DOC, returned: C:\Program Files\Microsoft Office\Office\Winword.exe.
>
>I am using a P400, Win 95 Version 4.00.950B and The new visual studio 6.0. The knowledge base article that came with MSDN visual studio 6 indicated that if the install program did not put quotes around the entry then the find executable would have a problem when the program had long path names with spaces. It could be that all of yours are installed and quoted properly, but some of mine are not. The one that does it all the time on my machine is the Adobe acrobat PDF reader.
>
>Hope this helps

Thanks for the update Brett. Just a quick question. If you double click on a Acrobat file in the Explorer, does the PDF reader start?