Question about VFP9.0 SP2 Report Engine

[foxlover2012]

When I use VFP 9 reporting engine, variable output goes to my form sometime behind objects like command buttons. My app sets SET TALK OFF almost on the first line and does not turn it back on. It is like VFP is turning on, sending variables output to my form and then cutts it back off. The only fix I have found is to SET CONSOLE OFF, print the report/label and then SET CONSOLE ON again. What is the fix?
Thanks, John
Does not happen if I switch to 8 report engine!

 

[Mike Lewis]

There are several possible things you can do.

Firstly, keep in mind that SET TALK is scoped to the data session. You say you issue SET TALK OFF at the start of the application. The problem is that, if your reports are running in a different data session, then that setting won't apply. You need to repeat the command in every form that runs in its own data session.

Alternatively, set the AllowOutput property to .T. That's something you should do for every form in your application. The obvious place to do that is in your base form class. Once you've done that, you should no longer see that kind of background output on the form, regardless of how it is generated.

Finally, instead of bracketing the REPORT FORM with SET CONSOLE ON and OFF, just add the NOCONSOLE keyword to REPORT FORM. Whether that will solve the problem in this particular case depends on what output you are using for your reports.

Mike



__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[Olaf Doschke]

I think you see a known bug of the reportoutput.app

Find the homepage of foxypreviewer on VFPX on codeplex.com, besides the download of foxy previewer it offers the download of a fixed community edition of the reportoutput.app and that would fix that problem.

Bye, Olaf.

 

[foxlover2012]

Thanks Mike and Olaf. Seems that the upgrade on Foxypreviewer fixed most of it. I still have a "1" appearing on my form, so I'll have to trace it down. John