It would appear that the activeX graph objects with their individual hwnds are grabbing the _vfp.Activeform preventing you from even checking the windowtype of the active VFP (modal) form even if you rooted out all set focus calls.

While I agree that it is probably a bug that VFP will even allow setfocus to another object outside of an active modal form, it is something that I have observed in all VFP versions that I have used. The first time that I had a timer fire that set focus to another object when a modal form was up, it took me days to finally figure out what was causing the application to hang. Now I rarely use modal forms.

I feel your pain, but if you can't trap (what should be at least an error or perhaps better, ignored) on setfocus outside the modal form, about the best you can do is report it as a bug and hope for a fix in the near future. Unfortunately, you will probably get an answer that this behaviour is "by design".