I have VB6 app that uses the MsComm activex control. The app is using a rs485 port (com3)at 155200 baud. When I change it to anything higher, say 128000 baud, I get "Could not set comm state, there may be more invalid comm parameters...". I've also tried 230400 baud. What's curious is that if I change the baud value in vb at design-time some of the values are accepted but fail at runtime (all other parameters are unchanged ). In other instances the new baud value is rejected at design-time when the mscomm settings property is changed.
Any insight into this problem would be appreciated. At this point I'm not sure if the problem lies with the MSComm activex control or the NI RS-485/2 card driver. I could switch to the NI activex control but it would be painful.
Regards,
Dan Quinones
