Todd,

I think I follow your comments about events that are raised by ax ctrls being queued by VFp. Autoyield is another of
those issues over which my eyes have passed but precious little penetrated beyond the cornea so thanks for 'raising'
my consciousness.

As I mentioned in my original plea for help, I'm trying to let the MSComm ctrl manage as many of the comm details
as possible, as it seems to do in VB, rather than impose loops to control communication. Within the OnComm
event code, there is only one loop (I'm not familiar with the 'tight' designation). That loop strips the message delimeter from a message that has been preliminarily parsed and recognized as a data message. Generally, there is only a single 'trailing' 'carriage return' to be stripped so this is a quickie if ever there was one but, of course, whether it impacts MSComm's ability to monitor the port and/or raise events, only the electrons know for sure.

Meanwhile, as I mentioned in my last reply, you've enable me to 'progress' to other errors and I'm working on them this weekend. (Life? I remember it only vaguely)

Again, thanks for your help.

Mike