Kurt, Personal email sent with Doug's fix included. Dave
-----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of Kurt Wendt Sent: 08 October 2012 15:39 To: [email protected] Subject: RE: VFP9-Reporting Hey Folks, I was just looking thru older posts that are sitting in my ProFox e-mail folder, and I came across this one that discusses the problem I have been having for a while now - which I know that MANY People experience. This is in regards to "a bug in the report designer that will flip the printer environment back on". I tried to go to the links below - however, here at work - I am blocked from accessing by Barracuda - as it thinks it's a Blog or Forum - which, of course, it is - but, it's a Techy Blog with Answers to problems - as opposed to a personal type Blog. So - is there anywhere else where I can get the answer - and get this Fixed once and for all. Since - EVERY Time I have a QA Tech install a Report update - and, if I Forget about the problem (which I fix by opening report Form in VFP 9 - even though almost all our Dev. is done here in VFP7) - then the client complains that they can't send the report to the right printer! TIA, -K- -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Kaye Sent: Thursday, July 12, 2012 8:02 AM I posted a little utility prg to the uploads section here a long time ago that strips the printer specific stuff out of a single FRX or an entire folder. There's a bug in the report designer that will flip the printer environment back on. Doug Hennig blogged about it some time ago and posted a fix that you can integrate into your own development environments. http://doughennig.blogspot.com/2010/03/fixing-report-designer-bug.html http://doughennig.blogspot.com/2012/02/updating-vfpx-reportbuilderapp.ht ml -- rk -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Carl Lindner Sent: Wednesday, July 11, 2012 5:40 PM Sytze, I ran across this problem last week. I used adir and looked for "DEVICE=" in expr. Out of 500 or so reports the problem appeared in 20 or so. I opened the reports and uncheched the printer environment. Crude, but it seems to have worked with minimal time invested. I could not understand why anyone would want to set it on. A post earlier this week indicated it was a bug in SP2 that was resolved with a hotfix. Carl [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
