If it has a network connection, I'd choose Winsock (actually
SocketWrench here). If serial's your only choice, MSComm.
There are many usage samples for either control so pick one and go to
PlanetSourceCode.com and just enter the name of the control in the
search box. It'll probably return a bunch of stuff you don't want but
you should be able to find at least a couple of good examples there.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
Thanks indeed, i would like to ellaborate my scenario a bit more.
There are at the moment 2 offices one's the Main office and other being the
Site, and the Site's where there are heavy duty machine with their own
processor. As mentioned earlier there's a RS-232 cable used to get the data.
There's No NETWORK.
The Client, asked us if they can dial and see the latest data that's
extracted from the machine.
I Suggested that then there'll be 2 apps running, one on the site, which'll
get the data, organize the data as per the given format, and store it in a
Database. and will then send to the site, via WINSOCK.
The Main Office in turn can have a Console Popped up to display respective
machine data.
Iam new to WINSOCK and MSCOMM, so bit of advise regarding them, and i'll be
highly greatful if something more on the solution can be given.
TIA.
------------------------------
Thanks indeed, i would like to ellaborate my scenario a bit more.
There are at the moment 2 offices one's the Main office and other being the
Site, and the Site's where there are heavy duty machine with their own
processor. As mentioned earlier there's a RS-232 cable used to get the data.
There's No NETWORK.
The Client, asked us if they can dial and see the latest data that's
extracted from the machine.
I Suggested that then there'll be 2 apps running, one on the site, which'll
get the data, organize the data as per the given format, and store it in a
Database. and will then send to the site, via WINSOCK.
The Main Office in turn can have a Console Popped up to display respective
machine data.
Iam new to WINSOCK and MSCOMM, so bit of advise regarding them, and i'll be
highly greatful if something more on the solution can be given.
TIA.
"Dick Grier" wrote:
> Hi,
>
> There no "better." Which you use depends on your physical connection. If
> you use a network connection, then certainly you would use Winsock (or
> equivalent). If you connect via RS-232, you would use MSComm (or
> equivalent).
>
> Now, if you have a choice, then a Winsock connection should provide
> substantially higher raw performance.
>
> Dick
>
> --
> Richard Grier (Microsoft Visual Basic MVP)
>
> See www.hardandsoftware.net for contact information.
>
> Author of Visual Basic Programmer's Guide to Serial Communications, 4th
> Edition ISBN 1-890422-28-2 (391 pages) published July 2004.
>
>
>