--
I was curious if implementing a SET PATH in my Main.PRG would make my VFP.EXE run better!:-)
--

Depends on your app code whether your *app* would run faster<s>. I don't think it makes VFP.EXE run any faster to set a path if your app otherwise has no reason to SET PATH.

---
My hope was that the code would reduce the number of system searches by the OS while my VFP exe was running.
---

It sounds like you're confusing the DOS/environment path with the VFP SET PATH. They are two different things. I may be misreading your comments, but it does sound that way.

By SETting PATH where you did not have one before, you're basically *lengthening* the places that VFP will go to look for certain code components, if anything.

You could set up OS path variables differently in a batch file or script that started VFP, I guess, assuming appropriate rights. But within VFP, within your app, your SET PATH isn't going to affect "system searches by the OS".

You might want to look at the FULLPATH() function and its optional nMSDOSPath parameter for an illustration of the difference.

One area you can use to speed up VFP, path searching wise, within your app, would be SET OLEOBJECT. You could limit registry searches by turning this OFF in some cases.

Other than stuff like this, I can't speak to your desire for logo compliance, because what you're trying to do with this syntax doesn't (yet) make sense to me <s>. Sorry...

>L<