>Hi Rick,
>
>PDF3 is derived report listener.
>All metadata (text, value, left, top, width, height) are the same for PDF3 and each report listener (base or derived).
>
>MartinaJ

First, please allow me to thank you again for your excellent work on CVP. The add-on to re-generate a LOG file with source code ... it's an invaluable tool I use regularly. If you have a "Donate" button somewhere, please post or email me a link and I'll send you a donation for the value I find in that utility. It's been a true asset multiple times, saving me man-hours of labor.

On PDF3, correct. I've found there's an algorithm in there designed to take text that should be wrapped and wrap it to multiple lines. I commented that block of code out and it's still wrapping, which makes me think it's something happening inside VFP when it's using this particular object for the reportlistener.

I'll try recording the values it uses for each position, and then switching back to FoxyPreviewer and seeing if it generates the same. And also I'll write a pass-thru listener to record the values to see if they're any different.

UPDATE: I will note that if I print to CutePDF it prints properly. It's only when it's generating to PDF with PDF3 that it prints improperly. I'll find out soon about FoxyPreviewer and report back.

>>I have discovered an issue with PDF3.PRG written by Martin Krivka in 2013: http://www.vfp.cz
>>
>>It was a replacement I began using for FoxyPreviewer because PDF generation is 2 orders of magnitude faster.
>>
>>It has an issue, however. It causes things to wrap differently than the normal VFP report writer does / would. I've been looking through the code but cannot figure out what is causing it to be that way (if it's PDF3, or if it's in the libhpdf230.dll functions it calls.
>>
>>I have been able to identify that if you have a right-justified field that receives a numeric input (as n(14,2) for example) and it's set to be a currency, and its value is something like "9876.54", then it will be received as many spaces, then the currency symbol, then the number. I believe these extra leading spaces are causing the issue. If I take off the currency symbol, it is received without leading spaces and it does not misalign on the PDF3 output to PDF file.
>>
>>Does anyone have any experience with this extra spacing on PDF3? Or know of a workaround?
>>
>>I also have the same issue on a long description column that is printed on the report. It may be longer than the actual width of the field I have for it, but if there is data there on the row that is wider than the field truncates on Visual FoxPro's report writer. But on the PDF generation, it adds an extra blank-line after it on all of the lines, like those extra leading or trailing spaces are causing a wrapping issue.