>>Dale,
>>
>>I can suggest a workaround. Create another layer on both client and server ends, dedicating a control on each end for the messaging. Send your broadcast using UDP on another port.
>
>What about the Winsock ports? Are they reserved - can more than one be used, or is the same one used - and contolled by who last instanciated the final tier in the loop?
>

Terry,

You can use any port you desire - as long as it doesn't conflict with any currently in use :-) I usually go to http://www.iana.org/assignments/port-numbers and find an empty one. This does in no way guarantee that that port may be in use by another app. A quick netstat -a from a command prompt will show you those. An expansion of my above - by adding an additional control on server and client ends, and dedicating these to the messaging function, you could use say port 53277 UDP to broadcast the message. All clients would be listening on the same port and respond to the message accordingly. It gets around the timing problem originally noted when sequencing quickly through the controls. Just another VFP/ActiveX aberration IMO. HTH