>George,
>
>Yup, this is one of those things were "being a good programmer" and truly defining your function bites you in the butt big time. This is a bug that I wish would get fixed sometime.

David,

Vlad's suggestion about SET PROCEDURE TO... (and I think Peter may have mentioned it too) does reduce the time. While I think you're right about it being bug, I can see why it could be by design. Consider the following scenario: Executable myexe calls myapp1.app and myapp2.app. Consider that both the apps have a call to an indentically named function (MyFunc) which are actually different, and return different results. When myapp1 calls MyFunc, it's loaded into memory. If, at a later time, myapp2 tries to call MyFunc, it may be actually calling the wrong function. If the FUNCTION statement causes the program to be cleared after calling, then this type of problem is eliminated. In short, and while I doubt it, it may under these circumstances eliminate some redundancy problems caused by identically named functions.