Weird...my app's reports run fine on Win7 but when trying the same app on Win10, I get no output....and no errors either. Just as though it has popped up and vanished immediately. Has anyone else had that experience with Win10 and a VFP9 app?
tia, --Mike
On 2017-05-24 22:21, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Weird...my app's reports run fine on Win7 but when trying the same app on Win10, I get no output....and no errors either. Just as though it has popped up and vanished immediately. Has anyone else had that experience with Win10 and a VFP9 app?
tia, --Mike
Re-sending....any takers???
mbsoftwaresolutions@mbsoftwaresolutions.com wrote on 2017-05-26:
On 2017-05-24 22:21, mbsoftwaresolutions@mbsoftwaresolutions.com wrote: Weird...my app's reports run fine on Win7 but when trying the same app on Win10, I get no output....and no errors either. Just as though it has popped up and vanished immediately. Has anyone else had that experience with Win10 and a VFP9 app?
tia, --Mike
Re-sending....any takers???
Mike,
Not I.
What are you using for the report viewer?
Tracy Pearson PowerChurch Software
On 2017-05-26 12:34, Tracy Pearson wrote:
mbsoftwaresolutions@mbsoftwaresolutions.com wrote on 2017-05-26:
On 2017-05-24 22:21, mbsoftwaresolutions@mbsoftwaresolutions.com wrote: Weird...my app's reports run fine on Win7 but when trying the same app on Win10, I get no output....and no errors either. Just as though it has popped up and vanished immediately. Has anyone else had that experience with Win10 and a VFP9 app?
tia, --Mike
Re-sending....any takers???
Mike,
Not I.
What are you using for the report viewer?
Just regular native reports, both in 80 and 90 rptbehavior mode.
Have you cleared the printer info from the .FRX?
Fred
On Fri, May 26, 2017 at 9:18 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-05-24 22:21, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Weird...my app's reports run fine on Win7 but when trying the same app on Win10, I get no output....and no errors either. Just as though it has popped up and vanished immediately. Has anyone else had that experience with Win10 and a VFP9 app?
tia, --Mike
Re-sending....any takers???
[excessive quoting removed by server]
There's also a setting in VFP for that. When you're in a report, the Menu for "Report/Properties..," and there's a check box to "Save printer environment". There was a problem with that getting checked automatically, but I think that was fixed in one of the service packs/hotfixes. A project hook would make certain that's dealt with. (belt and suspenders)
Fred
On Fri, May 26, 2017 at 4:56 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-05-26 12:36, Fred Taylor wrote:
Have you cleared the printer info from the .FRX?
Fred
My project hook is supposed to do that via wOOdy's tip from long ago. I'll double check that...perhaps somewhere along the line I disabled my pjx hook.
Thanks!
[excessive quoting removed by server]
On 2017-05-27 14:03, Fred Taylor wrote:
There's also a setting in VFP for that. When you're in a report, the Menu for "Report/Properties..," and there's a check box to "Save printer environment". There was a problem with that getting checked automatically, but I think that was fixed in one of the service packs/hotfixes. A project hook would make certain that's dealt with. (belt and suspenders)
Yeah I remember that.
There is still some condition in the editor that will potentially flip the printer environment back on but the fine details escape me. I think Doug Hennig may have blogged about it and posted a code fix but you will need to recompile the affected app.
The other thing that can make for quirky report behavior is when no default printer is installed in the RDP session. Combine that with a saved printer environment and VFP is not happy when it tries to use the default Windows printer to render the report.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fred Taylor Sent: Saturday, May 27, 2017 2:04 PM To: profoxtech@leafe.com Subject: Re: VFP9SP2 app on Windows 10 -- reports not showing
There's also a setting in VFP for that. When you're in a report, the Menu for "Report/Properties..," and there's a check box to "Save printer environment". There was a problem with that getting checked automatically, but I think that was fixed in one of the service packs/hotfixes. A project hook would make certain that's dealt with. (belt and suspenders)
Fred
On Fri, May 26, 2017 at 4:56 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-05-26 12:36, Fred Taylor wrote:
Have you cleared the printer info from the .FRX?
Fred
My project hook is supposed to do that via wOOdy's tip from long ago. I'll double check that...perhaps somewhere along the line I disabled my pjx hook.
Thanks!
[excessive quoting removed by server]
Found it.
http://doughennig.blogspot.com/2012/02/updating-vfpx-reportbuilderapp.html
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Tuesday, May 30, 2017 7:31 AM To: profoxtech@leafe.com Subject: RE: VFP9SP2 app on Windows 10 -- reports not showing
There is still some condition in the editor that will potentially flip the printer environment back on but the fine details escape me. I think Doug Hennig may have blogged about it and posted a code fix but you will need to recompile the affected app.
The other thing that can make for quirky report behavior is when no default printer is installed in the RDP session. Combine that with a saved printer environment and VFP is not happy when it tries to use the default Windows printer to render the report.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fred Taylor Sent: Saturday, May 27, 2017 2:04 PM To: profoxtech@leafe.com Subject: Re: VFP9SP2 app on Windows 10 -- reports not showing
There's also a setting in VFP for that. When you're in a report, the Menu for "Report/Properties..," and there's a check box to "Save printer environment". There was a problem with that getting checked automatically, but I think that was fixed in one of the service packs/hotfixes. A project hook would make certain that's dealt with. (belt and suspenders)
Fred
On Fri, May 26, 2017 at 4:56 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-05-26 12:36, Fred Taylor wrote:
Have you cleared the printer info from the .FRX?
Fred
My project hook is supposed to do that via wOOdy's tip from long ago. I'll double check that...perhaps somewhere along the line I disabled my pjx hook.
Thanks!
[excessive quoting removed by server]
Actually, that's about another issue Doug found and fixed. But it does link to this one:
http://doughennig.blogspot.com/2010/03/fixing-report-designer-bug.html
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Tuesday, May 30, 2017 7:42 AM To: profoxtech@leafe.com Subject: RE: VFP9SP2 app on Windows 10 -- reports not showing
Found it.
http://doughennig.blogspot.com/2012/02/updating-vfpx-reportbuilderapp.html
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Tuesday, May 30, 2017 7:31 AM To: profoxtech@leafe.com Subject: RE: VFP9SP2 app on Windows 10 -- reports not showing
There is still some condition in the editor that will potentially flip the printer environment back on but the fine details escape me. I think Doug Hennig may have blogged about it and posted a code fix but you will need to recompile the affected app.
The other thing that can make for quirky report behavior is when no default printer is installed in the RDP session. Combine that with a saved printer environment and VFP is not happy when it tries to use the default Windows printer to render the report.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fred Taylor Sent: Saturday, May 27, 2017 2:04 PM To: profoxtech@leafe.com Subject: Re: VFP9SP2 app on Windows 10 -- reports not showing
There's also a setting in VFP for that. When you're in a report, the Menu for "Report/Properties..," and there's a check box to "Save printer environment". There was a problem with that getting checked automatically, but I think that was fixed in one of the service packs/hotfixes. A project hook would make certain that's dealt with. (belt and suspenders)
Fred
On Fri, May 26, 2017 at 4:56 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-05-26 12:36, Fred Taylor wrote:
Have you cleared the printer info from the .FRX?
Fred
My project hook is supposed to do that via wOOdy's tip from long ago. I'll double check that...perhaps somewhere along the line I disabled my pjx hook.
Thanks!
[excessive quoting removed by server]
On 2017-05-30 07:48, Richard Kaye wrote:
Actually, that's about another issue Doug found and fixed. But it does link to this one:
http://doughennig.blogspot.com/2010/03/fixing-report-designer-bug.html
Perfect...THANKS!!!
-
Fred Taylor -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Richard Kaye -
Tracy Pearson