Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
FoxyPreviewer listener object reference for UDF
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Produits tierce partie
Divers
Thread ID:
01674531
Message ID:
01674533
Vues:
45
Thanks for the reply, you got me part of the way there.
I don't see _oreportoutput.item(x) as working - whatever integer I used could not be evaluated

But it got me thinking of some other code I found while searching...
What I ended up doing was loading the preview helper, which then populated the _goFP object with the listener information (_goFP.oListener shows .NULL. if I issue a report form command. However, once I sent to my client, it's asking for the .frx file....can I reference the invoice file without having to litter my client drives with .frx files?
Local loReport As "PreviewHelper" Of "redist\FoxyPreviewer.App"
loReport = Createobject("PreviewHelper")
loReport.Addreport("invoice.frx")
loReport.runreport()
*If I issue report form invoice preview, then _goFP.oListener shows as .NULL. in my UDF.
In my UDF, I have the following code
	Procedure groupPageCount As Integer
		Parameters pInv

		If Type('_goFP') = "O"

			If _goFP.oListener.TwoPassProcess And _goFP.oListener.Currentpass = 0 Then		&&set
	...
>Hi,
>
>Try use _oreportoutput.item(1).
>
>Or you can modify foxypreviewer.prg, part: * Create a PREVIEW listener
>
>MartinaJ
>
>
>>I have a report that needs to calculate some data based upon the reportlistener currentpass property. My UDF is called from the on exit expression in my group footer. Once in the UDF, I see that FoxyPreviewer creates a listener variable that looks randomly generated. When I created my own listener in the past, I had assigned it a variable upon creation and could reference that. FoxyPreviewer doesn't seem to do that. Does anyone know an easy way to reference the listener, or where the best place would be to add a reference to it in my application object at runtime?
Steve Howie, owner
DaSH Technology
Denver, CO
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform