Dragan,

Are you using TEXTMERGE or ?/??/??? to output this file? If so you may be getting hit by a side effect of SET MEMOWIDTH. I use VFP to build the web pages for the Q&A section of my website. I have SET MEMOWIDTH to 1024 with code like this:

* We need to chunk this out a little at a time here because otherwise just printing
* it as a memo SET MEMOWIDTH causes CRLF pairs to be inserted into the stream every
* MEMOWIDTH characters!

for i = 1 to len( lcData ) step 512
   \\<<substr( lcData, i, 512 )>>
endfor

I didn't find the problem until the CR/LF pair got inserted into a TABLE tag and hosed the display of the table.

>I have a couple of apps where users stick to FPD2.6 and have laser printers. All of them are either HP 5 or 6, and some are OKI 400, all using the provided Fox driver for HP III. It works well most of the time (if you consider using Courier only can be taken under "well").
>
>I have a slight problem. Sometimes, practically at random, it prints one line overlapped over the previous line. Most of the cases it's the line preceding a line where a horizontal line is drawn using hyphens or equal signs, but I can't take it as a rule. It happens once in ten or twenty pages. Maybe it's because I'm printing into a file and replacing some Epson codes (which were hardcoded into some reports) with appropriate PCL codes, and I replace the font sizes according to font attributes (i.e. if it finds chr(15), it emits a "18 cpi" instead, if it finds bold, it puts larger font and so on).
>
>I've looked at the hex dump and the offending lines look quite normal, having appropriate coordinates before each bit of text, and ending with regular cr+lf. Could it be the PCL is recalculating column/line coordinates into pixels, and miscalculating sometimes? Did anybody have this before?