>No, I am talking about setting it to .T. before and to .F. after.

I got it, thanks.
Not that I'm going to use it, though :)

>
>>Hi Alexander,
>>
>>Follow your logic, you should set this variable to .T. right after READ EVENTS in the first application.
>>
>>>Hi Nadya,
>>>
>>>No, I think the correction is right, because there may be a lot CLEAR EVENTS
>>>commands in the application in different places and I think there is a chance to miss one and our public variable will remain .T., like READ EVENTS command is still active. So, it is my though, the best place is to place it right after READ EVENTS.
>>>
>>>You are right, if we will speak in Russian here we will confuse others. Anyway, I think, writing in English is a very good practice to learn it.
>>>
>>>Best regards.
>>>
>>>>>Oops... made one stupid mistake...
>>>>>Please read as "right after READ EVENTS store .F."
>>>>
>>>>I think, your original post was correct :)
>>>>
>>>>BTW, as far as I know, there is no restriction for using only English here. I saw several posts in Spanish and few in French. I think, we can freely use Russian, but the audience would be small then. :)
>>>>
>>>>Best wishes,
>>>>>
>>>>>> ...
>>>>>>Before call READ EVENTS command in your first APP, define that public variable and store .T. to it, and right after CLEAR EVENTS store .F.. In another APP you may check that variable as follows:

If Type( "_READEVENTSINEFFECT") <> "U" And _READEVENTSINEFFECT
>>>>>>    && READ EVENTS command is issued
>>>>>>Else
>>>>>>    && no READ EVENTS in effect
>>>>>>EndIf

>>>>>>
>>>>>>Hope this helps.