[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 373
  • Last Modified:

_ReportOutput

A users machine gets an error message as follows:

Variable  '_REPORTOUTPUT' is not found

What do I need to do?

Thanks.
0
MichaelKatz
Asked:
MichaelKatz
  • 6
  • 3
2 Solutions
 
pcelbaCommented:
Are you sure you are executing the program in VFP9? This error can raise when you use _reportoutput variable in older VFP versions, so you should look at VERSION() result as the first step.

If this happens in VFP 9 then you have to post some code sample.
0
 
tusharkanvindeCommented:
Have you compiled the project in version 9.
0
 
pcelbaCommented:
Yes, exactly. Code compiled in older VFP version can produce this error because system variables have different representation in FXP module, so the _reportoutput compiled in VFP8 is trying to behave like a standard variable which is not available when running under VFP9.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
MichaelKatzAuthor Commented:
Definitely compiled in VFP 9.0 SP1

Code includes       SET REPORTBEHAVIOR 90 before running report.

and Iarun a small prg before compiling to replace the Tag and Tag2 fields with space(0), which I believe is recommended to avoid saving printer specific details.

Michael
0
 
pcelbaCommented:
So, when the error appears? Some code sample would help.

Also to replace Tag and Tag2 is not necessary because printer specific info is stored just in the case you check "Save printer environment" in the Report properties dialog.
0
 
pcelbaCommented:
Do you use _reportoutput variable in your app?  This also could be caused by ReportListener compiled in old VFP version.
0
 
MichaelKatzAuthor Commented:
Thanks, Ppcelba

You set me in the right direction. Setting report behavior to 90 requires some more info that the app did not provide.

I set it to 80 and it seems to be working fine.
0
 
pcelbaCommented:
Interesting. I just may guess the problem is hidden now.

I would recommend one thing: Update your VFP version to the latest SP2 (http://www.microsoft.com/downloads/details.aspx?familyid=a28ddec6-ba3c-49d0-8176-8c0b3fca06d1&displaylang=en) and apply available hotfixes (http://support.microsoft.com/kb/968409).

VFP9 SP2 help is available also.

You should also install the latest Xsource (http://www.microsoft.com/downloads/details.aspx?familyid=320B6438-BE76-48C7-A68E-1792E2AA3BF2&displaylang=en) with its latest updates from http://vfpx.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=6446
 
0
 
MichaelKatzAuthor Commented:
I heard that SP2 had problems with VISTA.  I don't remember if it was running apps on vista machines or developing apps on vista machine.

Any risks or downside with any of the above recommendations?
0
 
pcelbaCommented:
Original SP2 had some problems almost everywhere. It was solved by hotfixes and the current VFP version is: Visual FoxPro 09.00.0000.7423 for Windows.

I've installed SP2 on Vista and it works without problems. Others should confirm it. You may ask it in a new question to see experts opinion.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now