>Hugo,
>>>You think, it is still related to the subject "Send signals to each user using same system"? I would start the new thread.
>>
>>Actually, I think it does, why do you think it does not?
>>
>>In fact, we have implemented exactly what Naomi hinted, we have it working for a very small group of users (just 3 or 4 computers), and we are waiting to see what happens once everyone is using it before claiming success
>
>we may have to implement something similar in the future, and I'd be grateful if you could send me an update on the reliability of this approach. In theory it should get you best response time, but I worry (partially from timer event expirience<bg>) that the event may hiccup or not fire always - as long as enough intervals (or different timers) are in play I see timer usage as the approach "with safety net" - but less elegant.
>
>regards
>
>thomas

Hi Thomas,

I have forgotten about this post.

We are running now our maintenance warning and it seems to work quite well (although only for systray applications, we still need to work for the main application), each computer runs 1 or more systray applications that when we do the maintenance must be closed, and by listening to a file creation in a folder we were able to shut those applications down nicely. I never counted how many machines are responding, but a rough guess is that around 50 machines are responding to the event withing seconds. This is done in two steps as I mentioned before and to my knowledge all computers respond, but, as always there is a problem. If there was a network hiccough between the user's login and the time that the event is fired (and some times this might been days) then for the listener is hooked up to a network file and foxpro does not like network hiccoughs, then it might silently ignore all events.