Quote:
> Hi,
> I was expecting a different error if some other program
> had grabbed the port, do you know why it reports the error it does?
> <<
> Sure. The port is already open. The fact that it has been opened by
> another program, not your own, is a Windows issue. That is, Windows
passes
> that message to VB -- VB doesn't generate it.
Hi{*filter*}, since the port is already open as a result of another program I was
expecting error
8005 (Already Open)or 8010 (Not Available) rather than the 8015 (Can't set
comm state).
Are the other two errors only going to come along if MY software attemps to
open the port a second time etc. as opposed to a completely separate program
grabbing it?
Thanks again for the help, I bought the book, BTW, for future reference.
-Ralph
Quote:
> Richard Grier (Microsoft Visual Basic MVP)
> Hard & Software
> 12962 West Louisiana Avenue
> Lakewood, CO 80228
> 303-986-2179 (voice)
> 303-986-3143 (fax)
> Author of Visual Basic Programmer's Guide to Serial Communications, 2nd
> Edition ISBN 1-890422-25-8 (355 pages).
> For information look on my homepage at http://www.*-*-*.com/ .
> Use the Books link to order. For faster service contact the publisher at
> http://www.*-*-*.com/