Ah, local cash drawer (always) and local or remote printer? Is that what you're looking at?

>I thought about doing that, the problem is that the printer is typically shared on the network. In order to make that work I would have to create some sort of listener to pick up incoming network jobs and get them printed. I'm not wild about biting that off.
>
>
>>I'm running Win2k with VFP8/9 here, and once I assign the Generic/Text driver to a comm port, I cannot use that port with the MSCOMM control at all, whether there is a print job or not. So if OPOS is out, and you need this status testing of the drawer with MSCOMM, how about running your print jobs to FILE with the Generic/Text driver and send that file with the MSCOMM control? Would this screw up your app badly? Sending the file could be as simple as:
>>
>>Form.CommControl.Output = Filetostr("yourfile.txt")
>>
>>Or am I oversimplifying the problem?