My best guess at this point is that i need MSXML 4.0 installed on my testing machine or the distributed file to allow this to run?

I found the value for OUTPUTXML_XSLT_PROCESSOROBJECT in reportlisteners.h

If I try to run the following from my test machine it gives error 1733 when trying to create the loProcessor object on my test machine.

_reportoutput='reportoutput.app'
SET ENGINEBEHAVIOR 90
SET CLASSLIB TO HOME()+ "ffc\_reportlistener" additive
SET PROCEDURE TO \common30\hyperlinklistener.prg additive

loProcessor  = CREATEOBJECT("Msxml2.XSLTemplate.4.0")

I found an article on MSDN about this

'Including Report Files for Distribution'

Would i need to build a setup with installshield including the files msxml4sxs32.msm
and msxml4sys32.msm ?





>Hi Stacy.
>
>>Very strange, not throwing an error even...
>>
>>Maybe Doug will see this and jump in.
>
>I tried this both on my Dev PC and a test machine that has the VFP 9 runtimes installed, and it worked in both cases. You'll likely have to add some old fashioned debugging code (ie. WAIT WINDOW statements) to see what's going on. For example, in the HyperlinkListener class, add this:
>
>

procedure Init
>wait window 'Before DODEFAULT'
>llReturn = dodefault()
>wait window 'DODEFAULT returned ' + transform(llReturn)
>wait window 'This.HadError = ' + transform(This.HadError)
>return llReturn
>endproc
>
>procedure Error(nError, cMethod, nLine)
>wait window transform(nError) + chr(13) + cMethod
>dodefault(nError, cMethod, nLine)
>endproc

>
>Note that adding .H files to the project does nothing since those files are used at compile time, not runtime. Nor does having an ON ERROR, since _ReportListener has its own Error method, which overrides ON ERROR.
>
>Good luck!
>
>Doug