Jeff,

Check XFRX from http://www.eqeus.com/index.php. There's a version specificly for VFP9.

>I hope I'm wrong, but someone is going to have to prove it to me because I don't see it any other way.
>
>In a nutshell what I'm seeing is with 'set reportbehavior 90' if you print to a PostScript file and then distill it the 'text' will not be selectable in Adobe Acrobat 5 or 7. In fact, under Acrobat 7 when you do a Documents/Accessibility Quick Check it will tell you:
>
>"This document appears to contain no text. It may be a scanned image."
>
>I'm sorry, but that makes VFP 9 Report Behavior (RB90) completely useless to me and my customers. Whatever advanced reporting features it may have I can't use. My reports are data that will be consumed by users and used for other purposes like spreadsheets or other documents. Printing to paper is passe. Sure, Report Behavior 90 is great for paper or print preview, but that's not where things are at in this day in age. And having used WC where PDF is King RB90 is ok for reports that the user can only look at or print.
>
>Here's my repo:
>
>use (home() + 'labels') in 0
>select name from labels where recno() < 10 into cursor qlabels
>*create a report named junk and have one field on it, 'name'. Save the report.
>*Strip the expr and tag and tag2 if you want. It doesn't matter.
>set printer to name getprinter() &&and select either the Generic PS Printer or whatever other printer that will let you print a PS file.
>set reportbehavior 80
>report form junk to file junk80.ps
>set reportbehavior 90
>report form junk to file junk90.ps
>
>In Windows Explorer find these two PS files and Distill them or you can use whatever technology you want to distill them incluging the WC PDF class in code.
>
>View the resulting PDFs in either Acrobat 5 or Acrobat 7 or whatever version you have.
>
>Try to use the Text Select tool to snag some text in either and you will see that when RB was 90 it's not text and you cannot grab text.
>
>Please, my kingdom for a workaround!