It is. However, various printers have different paper widths and other characteristics. So what I designed for the characteristics of this particular model looks terrible on a different model printer that use impact printing [instead of thermal] and different width paper. I found this out the hard way.

>I thought oPos was supposed to be a "universal" pos solution. Whereas this is an Epson oPos solution. What gives? Can you use this implementation for Star and others as well?
>
>Thanks
>
>
>>>>>...is now available in the Downloads area of UT. Just do a search on my
>>>>>member ID. This PRG-based class of example code is designed for the Epson TM-
>>>>>T8II/TM-T88IIP receipt printers and cash drawers.
>>>>
>>>>Mark, just out of curiosity, what does this give us that OPOS doesn't? My memory of OPOS is too fuzzy for a good comparison...
>>
>>>It is a wrapper class for the Epson OPOS OLE Control. It is one of the few OCXs where you can programmatically AddObject() it to a form and not get the classic runtime error about improper or not found license. The rest is basically sample VFP code that is, IMHO, better representation than what is provided by Epson.
>>
>>>The class is not really intended to be a 100% fully functional, ready to drop in an app and go. It is sample code in a PRG-based class style format to give the developer a solid head start.
>>
>>Thanks Mark this should help me.
>>Good presentation last DFW fug meeting.