Anyone have experience with XFRX on a process server?

My process server executes queued jobs with at DO jobname.exe command. Each Job.exe includes its own FRXs.

Sample Jobs:
Job1.exe contains Job1Report.frx
Job2.exe contains Job2Report.frx
Each Job uses XFRX to generate a PDF
QMgr.exe issues DO Job1.exe, DO Job2.exe, etc.

QMgr.exe, Job1.exe, and Job2.exe alongng with the XFRX support files (hntlib.dll, msvcr71.dll, xfrxlib.fll, and zlib.dll) exist in their own folder. An instance of VFP fails when attempting to execute the second job. The same job can be executed multiple times simultaneously, but an error is thrown as soon as a different job is executed. The error message box contains "Job2Report.frx not found!" and bypasses the VFP error handler.
The same error occurrs in runtime as well as development environments. I get the same error in VFP6 as well as VFP8. I'm using XFRX 10.2.


This fails:
Start VFP
CD folder_name
DO Job1.exe works fine
DO Job1.exe works fine also
DO Job2.exe fails with "Job2Report.frx not found!"

In a runtime environment, QMgr.exe executes the jobs with a DO Job1.exe. I tried compiling the FRXs into QMgr.exe and excluding them from Job1.exe, but this failed at the first execution.

Apparently XFRX expects the FRX to be included in the same project with the program that makes the call to XFRX. And once it finds a frx, it saves the location and looks only there for subseqent reports.

Of course, if I compile all source files into QMgr.exe (Job1Main.prg, Job1Report.frx, Job2Main.prg, Job2Report.frx, etc.) it works. But that would mean distributing a new QMgr.exe every time a job was updated or created.

I suppose QMgr.exe could RUN/N Job1.exe instead of DO Job1.exe, but that would mean having to setup the environment on each job and it would be difficult to manage the job's progress from QMgr.exe.