>I have a communications EXE running on WinNT 4 Workstation. It is written in VFP6 and uses MSCOMM to read a serial port in a loop 24 hours per day. Currently the EXE is hogging the processor time, how allow NT to respond to user events without slowing down the EXE too much.
>
>I thought I saw a solution to this posted within the last 2 months, but I can't find it at the moment.

You can put a DOEVENTs within the tight loop.

You can add something like an INKEY() to the loop - even if you do nothing with it, it will allow windows events to be processed. If the poll rate of your app is critical (ie if a delay results in dropped data) neither of the first two solutions is very good.

You can adjust the priority of the VFP executable with Task Manager.