>>Had a client ask me and I have no clue. Can FPW 2.6 monitor COM1 for an Interrupt, like INT4? If so, how?
>>
>
>Not by itself; there's no provision for directly monitoring a port in FPW or providing a Win16 ISR, but you may be able to use an add-on like CommTools if it supports interrupt-driven comms. A more promising approach would be to write your own comms and use the DDE interface to control conversations between an FPW app and the communications app. FPW has the ability to act as either a DDE server or client.
>
>VFP could provide event-driven comms using the MSCOMM32 control in conjunction with VFPCOM, to expose the OnComm event of MSCOMMLib.MSCOMM to a custom VFP object, binding the VFP object to the MSComm object using VFPCOM's BindEvents()
>
>>Thanx for your continous support.

Thanx for the answer. The research I've done has pointed me in that direction. Unfortunately the client is FWP 2.6 until they can rewite the app in VB.