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

>Hi Dave,
>
>You run your app via a desktop link, yes?
>Where are the DLLs stored?
>If you run the app directly from explorer in it's folder (not via link), what happens?
>Generate an global ON ERROR that gives better error return, and compile with Debug Info on.
>
>Lutz
>
>>Folks,
>>
>>A VFP application I've developed generates an intermittent error when the program executable is run from its desktop icon. The program error is ‘Operator/Operand Type Mismatch.’ (see image). When this error occurs, the program fails to run.
>>
>>What’s frustrating and confusing for me is that this error sometimes happens and sometimes not. When the app fails to run, it’s commonly due to an open file folder window or an open window for an FTP internet location. The program run will only run after closing these windows.
>>
>>I suspect this issue relates to the application not finding the VFP Run-Time Resource DLLs (e.g: VFP9RENU.DLL) or not finding the correct DLLs for the application. But why this happens is a mystery.
>>
>>Can anyone advise on what’s causing the problem, and more importantly, what the solution is.
>>
>>Any guidance is welcome,
>
>
>>Dave
>>
>>ps. I do have the executable path set in the icon’s “Start In” property.