FoxyPreviewer Variable _REPORTOUTPUT Not Found

[John Stephen]

I have used FoxyPreviewer for years and have never encountered this problem. It happens when I run a second executable, but with all the exact same code as the first. I wonder if this is not allowed. I have paid for my download and I have a serial number like this:
_Screen.oFoxyPreviewer.cUser = "ASTARLA1"
_Screen.oFoxyPreviewer.cSerial = "*******"
_Screen.oFoxyPreviewer.nRenderMode = 2
I am running version 299 and I always initialise in the main program on startup
TIA
John

 

[Chriss Miller]

Version 299 is free - the last free version. So why did you license that? If you license FoxyPreviwer, then you license version 3 or higher. Switching to that might solve your problem.

Technically, I don't see why a second EXE couldn't use foxypreviewer with the error _REPORTOUTPUT not found. First, it must be about the value of _REPORTOUTPUT not found, not the variable itself, that's a system variable that every VFP process has and it's private to each process, i.e. both processes can set it to different values.

What seems out of whack is the value of _REPORTOUTPUT in the second process. What are you doing to start foxyPreviewer? Before setting the _screen.oFoxyPreviewer properties.

 

[John Stephen]

Hi Chriss
I think I paid because you asked for a donation, the zip file I downloaded was FoxyPreviewer v299z41.zip. and my current version is FoxyPreviewer v3.00.247 2023.12.10. I see you now have version v3.00.345
I have a central function I use to initialise FoxyPreviewer with serial number you gave me at the beginning of this post. I have never had this issue in any other code I have used and it is running fine in my other executable. I try not to change versions too much because I have 18 clients and it is quite hard to keep track of who has what.
The function I use to produce invoices is this, the nFoxyversion variable is what I use to keep track of my clients. I just call this function when I email an invoice. My clients are a funny lot and some just refuse to upgrade.
FUNCTION MakeFoxyPdf
PARAMETERS mReportName,mDestination
WAIT WINDOW NOWAIT "Generating PDF File"
IF nFoxyVersion >=3
DO FoxyPreviewer.app WITH "CLEAN"
_Screen.oFoxyPreviewer.cUser = "ASTARLA1"
_Screen.oFoxyPreviewer.cSerial = "198-299-XXXXX"
_Screen.oFoxyPreviewer.nRenderMode = 2
mFullFoxyVer = _Screen.oFoxyPreviewer.cVersion
SET REPORTBEHAVIOR 90
REPORT FORM (mReportName) OBJECT TYPE 10 TO FILE (mDestination)
DO FoxyPreviewer.App WITH "RELEASE"

I know you said that I don't need to use RELEASE, but mine is a multi company system with each company data held in sub directories. My clients tend to change companies on the fly with the program running. and for some reason (even though I close all files when changing) if they are doing reports data from the old company sometimes comes through. Using RELEASE seems to solve that issue. My second app (the one with the issue) runs independently of the main one.
Cheers
John

 

[Chriss Miller]

I don't offer FoxyPreviewer. I also never asked for a donation, I might have suggested you better use version 3 for your concerns and for easier usage in some aspects.

The only thing I consider wrong in your code is SET REPORTBEHAVIOR. When you start DO FoxyPreviewer.app WITH "CLEAN" that'll take care of both the REPORTBEHVIOR setting and also the _REPORT... system variables. So no need to care for that yourself. FoxyPreviewer always switches to 90 mode. It won't cause an error, it's just already at 90 mode when you do. It doesn't explain why you get the error.

You're not telling what nFoxyVersion is, it seems to indicate the foxy previwer version, so should be 3, but is it?
And where does the error come up? Do you have an error handling that tells you the error line?

 

[ggreen61]

I hope that you did not use your actual serial number in the post above...

 

[John Stephen]

Yes I have tried all of those things, but in the end gave up because my client was on downtime
Thanks anyway, I have switched to XFRX for that particular app. My main app runs fine on FoxyPreviewer
Cheers
John

 

[Chriss Miller]

You seem to aim for a solution without giving any necessary details about the problem. Good that you could solve it by swapping out FoxyPreviewer with XFRX. You should ask staff to delete your serial number from the post.

 

[John Stephen]

You seem to aim for a solution without giving any necessary details about the problem. Good that you could solve it by swapping out FoxyPreviewer with XFRX. You should ask staff to delete your serial number from the post.

I am sorry, I was in full on stress mode with my client staff idle. I tried everything I could. I have no idea how to get staff to delete anything

 

[Chriss Miller]

Tek-tips staff, not your staff. Inform them to delete your serial number from the forum.
You report your own post and as reason specify that you unfortunately posted a serial number that's not for the public.

 

[John Stephen]

If you looked at my post properly and my previous posts, I was talking about my client's staff being idle, not mine. Truth is I don't have any staff, I am a one-man band.

 

[mJindrova]

Variable _REPORTOUTPUT is a system variable and exist in VFP 9/A.
The error message can be confusing.

 

[Chriss Miller]

Your clarification is pointless. It has nothing to do with either your or your customers staff. I talk about tek-tips staff. I explicitly stareted my last post with tek-tips staff, didn't I?

If you don't understand what it means if you simply post a serial number, then just think about it. You will be taken responsible, if foxypreviewer makes no more sales at all. How can you be so ignorant about it?

And by the way, Even if you could still edit your post and delete it yourself, anyone can view previous versions of edited posts. You have to report and aks tek-tips staff to remove the leaked serial.