George:

See my other email entitled "PDQCOMM32 Works only for VB". I downloaded it last night and had severe difficulties with it. It does not seem to work in VFP, either under Win NT 5.0 beta or Windows 95. Tech support says they never heard of it working in VFP. They only test for VB. Yet you are recommending it. So it must work for you. What are you doing that I am not??

Kenn Leland/The Software Connection/Orange County California

>>>I am using the mscomm control to talk to a piece of equipment. This all works fine. My problem is that often the client that is running my app will have hyperterminal running and connected to the port that my application is using.
>>>
>>>My question is: Does anyone know of a way to check and see whether the comm port is available or not? Right now the only way I know that the comm port is in use by another application is when I get an error trying to open the port. Using the 'portopen' property doesn't work because the port is not considered open until opened from VFP.
>>>
>>>Any help would be appreciated.
>>>
>>>Thanks,
>>>George
>>
>>You could *upgrade* to PDQComm, which includes TAPI calls. This allows you to check the port status, and get other windows TAPI information like PreDial digits, area code, etc. Since PDQComm and MSComm were both written by Crescent division of Progressive, they are nearly substitutable.
>>
>>HTH
> I will definitely look into this. Thanks for the info!
>
>George