>>>>>>>Is there a way to do this? I have data coming in that gets displayed in a form that is open (one of many) but I do not want it to take focus away from the other forms in an app that are open unless the user intentionally clicks on the form. Whenever I refresh the form (it has two grids of data), it takes focus.
>>>>>>
>>>>>>Are you sure there's no .SetFocus() in the code? Also, when that form is deactivated, was the focus on the grid? Refreshing a grid which has the focus, while busy elsewhere, has some weird side effects sometimes (i.e. I have no clue what it may do, but moving focus off it may help).
>>>>>
>>>>>Pretty sure. I searched through all levels for any setfocus and activate.... I found a way to set focus back to the form that was open and had focus when the other form launches or refreshes the grids. I would rather the updating and efresh of the grid didn't grab focus at all...
>>>>
>>>>Couldn't it be that you have a setfocus in the grid's superclass on refresh? I know, it wouldn't make sense, but a refresh alone should not activate the form. I have a similar form also with a grid that works well on refresh.
>>>
>>> I resolved this in the activate of the form...
>>
>>All, I would still prefer to prevent the form from grabbing focus at all unless the user clicks on it. Right now I am setting focus to the calling form in the activate of form #2 (the called form with the grids), but still focus goes away from form #1 briefly and then there is the issue of cursor position when it goes back and if the user has moved to another control (I catch currentcontrol when the 2nd form loads but may have changed before it gets set back)....
>>
>>any ideas on how to make a form not take focus away from where it is called from unless the user clicks anywhere on the form after it loads?
>
>Here is a different approach. It allow multiple applications to work as a single application. When somethhing changes in one application, the other applications are notified of the changes and some action can be preformed.
>
>http://www.glrsoftware.com/download.asp#sharedcontext.zip
>
>It uses an Out-of-Process COM object to allow the different Apps to communicate with each other. The Word document will tell you how to install and how it works.

Thanks so much and I will look at it. I would prefer to not go that route as I already have events firing in the VFP app via com interop from events in a .net DLL. Com is used in many other cross-app communications as well. this form is purely VFP, within the VFP app so I would prefer that it stay that way for simplicity sake. I am curious of your approach so I will look at it !