>>>The function is also only ever declared once rather than repeatedly as you sometimes see when people want to make sure it is declared, since DECLARE definitely carries a performance hit.
>>
>>I don't see much of a point in considering a performance hit. Whatever you call with shellexecute() will surely last at least one order of magnitude longer than the registration of the call. Not that anyone calls this in a tight loop. And then, even if someone would, well, declare just before the loop.
>
>PMFJI. My goal is to eliminate the error message "file shellexecute.prg not found." The amount of time the application saves or not saves is not important for me at all. I have not yet implemented the code suggested by Lutz. But my impression - correct me if I am wrong - is that his code would eliminate the error code; not simply make the call to shellexecute more efficient.
All true and right. Note that I limited the quote to only the part I was commenting this time. The thread is already getting rich, so I'm trying to separate this subthread from the main branch.