>>>I get this too, however I launched it from the toolbar. No error occurs that's visible (no dialog).
>>
>>I found it does not matter how you launch the Task Pane, you can still detect the error using AERROR()
>
>What made you think of checking this? I haven't noticed any strange behavior with the Task Pane recently, and it seems as if the error may be spurious.

AFAIK, this error does not affect how the Task Pane behaves. It's just that I was expecting VFP to startup clean with no initial error info.

I was having a self-inflicted problem with a form where the error message returned by AERROR made no sense [the error produced by the Task Pane as it turns out]. So in my testing, I decided to quit VFP, restart VFP, run AERROR to make sure I had no VFP Startup errors, and BAM! There it was. I have had problems in the past where I got confused by AERROR because there is no way to clear the error info during a VFP session without having the Quit VFP to begin with. So, now when I debug, I usually issue ERROR 3 or some other bogus error [like ERROR 2] so I load VFPs error info with an error I know I am not going to get.