>>>>>>>>Thank you, Vladimir. Your approach will work.
>>>>>>>
>>>>>>>The messagebox has the wrong message, but I also don't see a better way. Probably search inside the project files?
>>>>>>
>>>>>>The approach Vladimir suggested works.
>>>>>
>>>>>Yes, but this is rather expensive approach. Who knows what do you have in the function? What if you completely change environment settings or do something else of this sort (say, zap bunch of important tables)?
>>>>
>>>>The function performs a rather simple task. And if the function does not exist, it won't cause an error down stream.
>>>
>>>If you need to invoke this function anyway, then wrap it in the try/catch. But if you just want to make sure that function exists (for whatever reason), but don't want to invoke it, then this approach is problematic.
>>
>>Interesting suggestion. The only downside I see is since I need to (if I need to, based on some other parameters) to call this function 2 or more times I would have to have 2 or more TRY/CATCH cases. Whereas if I determine (at the top of the routine via one TRY/CATCH) that the function does or does not exist, then I can call it as many times without using TRY/CATCH.
>
>I think being proactive (turning TRY/CATCH more) is a good approach. Alternatively, in the first call you can set some global logical var (_screen.MyFunctExists), so to not call this function later.

Yes, this could probably work. Thank you.