>>>I found that calling XFRX ("XFRX#INIT") in the EXE before calling it in APP solves the problem. Apparently when VFP caches the XFRX in .EXE it works on both the .APP reports and on .EXE report.
>>
>>No, it only works because in APP you run external reports. If you try to run reports embedded into APP, you'll have the same problem.
>
>Not exactly. What I do when running my reports in APP is I first copy them to the hard drive and then run report/XFRX against a temp copy on the drive.

I'm not sure what your point is. They are external reports for VFP.