Just one question about the timer event. When it fires, do you reset the timer immediately, or do you turn it off while the processing is taking place and then turn it back on? If you don't turn it off, that might be giving you a problem.

Dana

>> Well, before we find the reason, I wouldn't speculate. :)
>
>Well said, Michael.
>
>I do not know how to fix it. Actually, my message to the forum - it's a my "Last try". The problem was found about half year ago. I spend a day and did not find a solution. I have fixed it by very stupid way : I have put a "ThisForm.SetFocus" instruction into Deactivate method of every modal window that can be called from the Process screen. It worked well until we have translated our product to another languages. We have used INTL toolkit. Here the problem : INTL use modal forms instead standard MessageBoxes. So, it does not work together with my dirty patches.
>
>I'm out of ideas.
>
>
>>Well, maybe you could have the robot process to run in one app and the user
>>input on the other app, both 50% of the screen. :) Or, issue some kind of
>>automation COM object being launched from the main app, where you would
>>preserve the control from the main app, and maybe it would react better.
>
>The life is more complicated. The application takes one display in two-display system. Second display is used by another application (WonderWare). And I use "some kind of automation COM object" :-) to make them work together.
>
>And second reason: the product leave already about 8 years (it was started, I belive, in FoxPro 2.x). It's absolutely impossible to rewrite whole code to avoid a VFP b... feature.