>>Lutz,
>>
>>Your suggestion of trapping for ON ERROR earlier in the program tipped me off to the issue. It related to a function I run at the very start of the program launch to verify another instance of the application was not already running. That code had the Operator/operand error, but would only happen under certain conditions. Easy fix once I knew where the line of code for the error was.
>>
>>My app was trapping for ON ERROR, but that occurred later in the launch procedure. And the bug was happening before that.
>>
>>So nothing to do with the program not finding the run-time resources.
>>
>>Thanks again,
>>
>>Dave
>>
>
>BTW, I also saw it right away that it was code related :) The error message itself was very informative. You would have gotten a different error in case of not finding run-time libraries.

Sure. I only disliked to pointing out the obvious.
;)