>>>When printing a VFP9SP2 report to a virtual PDF printer like win2pdf or cutepdf, the text is converted to an image. Does anyone know how to send the text as text?
>>
>>Did you try XFRX or any other way to produce PDF from the report? Also what REPORTBEHAVIOR you're using?
>
>
>I've always had problems with FRX2Any not rendering my complex reports correctly. I was told by Marat (the owner?) that the new Listener implementation with ReportBehavior 90 would fix the rendering issues. Well, I put off moving to ReportBehavior 90 until this year, but finally got it implemented. And what do you know: rendering issues are still there (just different ones). I paid for the source code version of this product and it NEVER worked properly. Marat is a nice guy, but this product just can't handle complex reports.
>
>So I have given up on all of the FRX to PDF tools. My reports, evidently, are just too complex for these tools to render to .pdf properly. So I decided to go the virtual PDF printer route and now ReportBehavior 90 is coming back to bite me in the a$$.
>
>As cool as some of the new features in ReportBehavior90 are, the slowness and other quirks just aren't worth it. Back to ReportBehavior 80 here I come!!!

Just for kicks, download here print2pdf class - and take a look at the .ps you get (there's a property you can set so it doesn't get deleted immediately after use). If you can find your text in it (near the end - .ps is notorious for half a mile of prologue and then five inches of content), then you should still have the text in .pdf once GhostScript churns it out. I guess your [fox|windows|PDF printer driver] detects that the fonts you use don't exist in the printer, or are generally trying to do something the driver doesn't know how to explain to the printer, so text is rendered into an image instead and sent to print as such, but can't know without such a test.