Hi Mike: One thing you can do, is convert your report to text with FoxBin2Prg (right-click > Send to: FoxBin2Prg), take a look to see if you found something "strange", check that the Printer info is not there (you can modify this test if need to) and regenerate yor report from the text again with FoxBin2Prg
I think you loose nothing trying it. Download link: https://vfpx.codeplex.com/releases/view/116407 Doc and setup: https://vfpx.codeplex.com/wikipage?title=FoxBin2Prg Regards.- 2015-06-12 11:53 GMT+02:00 Mike Copeland <[email protected]>: > Thanks, Ted. That's pretty much my solution of last resort. Now that I > think of it, if I had done that at the beginning, I would have saved time > (assuming it solves the problem.) > > Mike > > Ted Roche wrote: > >> If it's always that one particular report, I'd poke around the FRX. >> Open it as a table (after making a backup, of course), and see if >> there are deleted records that might be getting confused with the >> correct ones. Pack it and see if the problem recurs. Open the report >> in the designer, select all, copy, and paste into a new report. (Of >> course, if you're using Data Environments or Listeners you'll need to >> modify them too). >> >> Nothing else works, rebuild the report from scratch. >> >> That's what I'd do. >> >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAGQ_JumpVP01yk4QDmKQ5DVZOy7c6J=dj7vsyyekb1ukrt1...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
