If you can live with plain ASCII text, send the report to a file from VFP (REPORT FORM whatever TO FILE filename ASCII) and then use low-level file functions (FOPEN, FGETS, FCLOSE) to open and read the file, and send each line directly to the printer with the ??? command. To take it one step further, you don't even have to use the report designer to create the report, instead you use TEXTMERGE inside a loop. This should give you the control you need to match up to the 10-cpi, 6-lpi kind of thing we all used to do with DOS and tractor-feed forms. BTW the ??? command bypasses all Windows printer drivers so you don't have to be concernced with which one to use.

HTH,
Rick

>We develop apps for users that produce tickets and invoices on old fashioned, pre-printed forms on tractor feed printers. The VFP report designer gives us fits with these forms. Many printer drivers don't allow the form sizes we need, and setting a user-defined size only works consistently if we use the basic Generic Text Driver. We usually end up creating a temporary report cursor with each record representing a formatted data string (line) to be printed. Then we use a report form with one detail line. We set the printer to the Generic Text Driver with Continuous, No pagebreak. We adjust the number of records to make the data come out on the right line of the form. This is a huge, time consuming pain. Does anyone have a better approach? Any help would be much appreciated.