The MSCOMM control included with VB5 is not
a TAPI control. Whenever it is used in an app.
it seizes control of the comport. That is not correct
TAPI behavior. Maybe, in a future release Microsoft
will give us a control that is more TAPI compliant.
A TAPI compliant control would sit in the background
and monitor the port(s) and be able to intercept messages and release
control of the comport(s) to
other TAPI apps. that is the downfall of the MSCOMM control.
>With Enterprise (pro too?) version of VB5 there is the MSCOMM control which
>uses TAPI, although it is pretty limited.
>3rd party vendors are also an option, but they can be a couple hundred
>bucks; but they have a lot more functionality.
>Hope this helps.
>>I am developing an application that will require tapi functionality. I am
>>using NT 4.0 and VB 5.0. I am looking for VB type definitions (.dll).
>>anyone give me a clue as to where I can get this.
>>I have tapi.dll and tapi32.dll in /winnt/system32/ but I can't resource
>>these for use within the application.
>>I have seen reference to tapi3.dll but can't find this anywhere. I also
>>have heard that tapi 3.0 is in the NT 5.0 beta but I don't want to
>>Any help would be greatly appreciated.