>Hi George,
>
>The client's app prints to HP4 laser or Epson-compatible dot matrix printers. The reports are either 10cpi or 17cpi fixed fonts.
>
>From what I can tell, all the PDSETUPs are doing is feeding printer initialization codes prior to a PRINTJOB. If necessary, I'll write a wrapper function to do that manually and comment out the PDSETUPs.
>
>I was just hoping there was some way that VFP still directly supported this function. Either way, it's not worth killing ourselves over this.
>
>Regards.

Hi Al,

I did have one more thought on this subject that might be of interest. By default, GENPD.APP used a C library (DRIVER2.PLB) unless you went in and modified the line: _PDRIVER = to indicate the DRIVER.PRG file. The problem is that DRIVER2.PLB is undoubtedly 16 bits (which VFP can't use), and it's a DOS library (more problems). This may have caused some of the problems you experienced.

You're right about GENPD feeding the initialization codes. Unless, however, the reports are hard coded, utilizing the Windows drivers is probably a much better idea.

One thing you might want to note. Using the Windows drivers may increase the amount of time it takes to print the report (especially with the Epson dot matrix). The way around that is to use the Generic / Text Only driver for the printer, entering the proper escape sequences.

hth,