Funny you should mention that. Doing barcode labels with Zebra hardware is my current app that I am working on. One of the main reasons I am doing this app is that the client previously used a label generation package that would NOT use Zebra's drivers, only their own 'sort of' compatible drivers - which have a tendency to lock up the printers which is obviously not good in a just in time production line. The REAL Zebra drivers (provided by Zebra) work as any other Windows print driver, although in the settings there are a lot more options. I'm not sure if you can access these programatically, but once configured you can just print like any other Windows printer, obviously with paper size limitations.
As far as printing barcodes, only Code 39 doesn't require special encoding. I am using a barcode font package from ID Automation, www.bizfonts.com. They have very generous licensing terms and have fonts for just about everything, all common bar codes plus OCR and MICR. Licensing any of their fonts entitles you to download their utilities, including an ActiveX control that does the encoding. They list VFP as being supported by their ActiveX control. Other utilities include UFLs for Crystal Reports as well as add-ins for Word and Excel.
In my application, I am generating the labels via Crystal Reports since the client will be creating additional labels besides the initial set included in the app, and they already are familiar with creating report in Crystal. But there's no reason why you couldn't use the activex control and native VFP reports.

hth,
Randy

>2 questions about barcoding.
>
>1. Has anyone had experience with printing to a Zebra printer from a VFP app ? Does it behave like a normal printer in Windows ?
>
>2. Can barcode fonts be used to print barcodes in fields on reports ? Is it that simple ?
>
>Jamie O