>The reason is that SrmReceiveCheck says there is a byte > available when the port is first openened, even though there isn't. You > then go to read it, but nothing is there and you time out (or hang if you > pass in -1 for a timeout to the read call!). I think most apps just ignore > the error, so it didn't matter (unless you are thorough and error check > every call you make).
Flush the receive queue just after you open the port, you won't have this problem. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
