>Hi Michel !
>
>OK, you are right, but I see, that other application besides VFP still got
>systemmessages because they run in the background independently the user actions.
>My problem is, that I dont understand, why VFP stops NullEvent during some user actions.
>
>BB
>
>>>I am working on a timer solution. I have found that VFP timer control doesnot get event during long statements like SQL select,
>>>and user actions (mousebutton down on window title etc.)
>>>I wrote an fll, in which I use the NullEvent to check the elapsed time, and if an interval is over it fires a UDF. (Time resolution 1 sec) It works under normal VFP statements like SQL select (so it is good for animated thermobar bmp-s, which has no affects for the select performance - max 4 percent slower). But ...
>>>VFP NullEvents doesnot come under some user actions. So, if user push down the mouse button my timer event isnot fired.
>>
>>In Windows, no matter what we'll do, we'll never be able to rely on something that will never miss one event. This is just the way Windows is.
>>
>>Many factors can affect that. Here, you have SQL. It can also be another application doing an intensive process or just to start another application.
>>
>>However, what you plan to do might help a little bit, however it will not work 100%.

Bela,

There's one instance where the user can actually override a timer's firing (and everything else for that matter). If the user simply presses the ALT key, which will turn control over to a menu, the timer won't fire. Even the a screen saver won't run.

George