I believe there is a communications control that you can use, though I don't recall what it is called.
Just as there is a Common Dialog control you can use to present the Print, Save, Font, (etc.) dialogsâa control that does not show at run-timeâI believe there is a similar control for serial communications.
Ultimately, in a Windows environment, Windows owns [u]all</u> I/O devices, and you must get Windows to permit the communications. This sort of thing is done at the driver level, not at the program level. That's why you need some intermediary, like this control I'm trying to remember the details of.
I highly recommend you search down that avenue, and retain such hair as you have left...editThe control I'm thinking of is
C:\WINNT\system32\MSCOMM32.oca, âMSCommLibâ (Control Typelib Cache). Also there is
C:\WINNT\system32\MSCOMM32.ocx, the actual MSComm control.
This might be a really tough undertaking in Access. But you can use this control in VB6. Do you have Visual Studio?
|