>>Hi Gang.
>>
>>We need to find a replacement for SilverWare, to go from 16 bit to 32 bit, to handle Modems.
>>
>>Anyone got any suggestions.
>
>What does SilverWare do that you can't with MSCOMM.OCX, we've used in the past with modems (long time ago) and we are still using it for serial communications. (I think we had SilverWare before I started working here, but I never used it)

Or the Windows API... (yep, ended up using API calls to get serial port and WinSock interface - most of the details are incorporated into their respective class libraries). Of course, since I was using such low-level access to serial port, I ended up having to deal with messy details of fiddling with modem initialization strings on a per-installation basis. Actual dial command is the easy part, the hard part is modem initialization string -- due to their brand and model-specific nature (or more specifically, the chipset of firmware version). Usually to get a reliable and predictable connection, I usually have to "dumb down" the modem by turning off features such as data compression and/or error detection/correction -- something that modems may agree on being able to do, but not always agree on particular method (it's sort of like two folks speaking English -- if one uses American English and the other British English, most of the time they're able to understand each other, but there are occasions where they might not understand each other).