I think SComm32 is written in VB6, hence the question!
Also what other dependencies do SComm32 needs other than VB run-time?!
Posted on: May 24 2017 at 02:34:51 AM
P.S: I am evaluating it right now and as far as I can tell it is working just fine at lease it does not give '8020' error as MSComm does, but I am comparing it with other components.
Posted on: May 24 2017 at 06:27:42 PM
Everything it needs such as runtimes etc is included with Windows so you should just need to deploy the OCX.
Performance should be very similar to MSComm32. There's probably some situations where it's quicker than MSComm and other situations where it might be a little slower. I've heard some people say that there can be a slight delay of a couple of ms between data hitting the serial port and SComm32 triggering an OnComm event. (MSComm32 triggers the OnComm quicker) but then SComm32 is quicker to read the data out of the receive buffer.
Under some conditions (if you call DoEvents a lot) then MScomm32's OnComm event can become re-entrant meaning another oncomm event is triggered while a previous one is still being processed which confuses the CommEvent property. Scomm has some Mutex on the OnComm event so another is never triggered while one is already running. Handling/setting up of that Mutex may be the reason for the few ms delay I mentioned earlier.
All in all though SComm32 is a good alternative to MSComm32 and it seems to be supported with updates as new versions of Windows is released
Posted on: May 24 2017 at 07:06:07 PM
Thanks a lot, I am satisfied with it till now.
I will replace MSComm with SComm32 in my current application and test it in the wild and I will order it as soon as it pass the test.
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.