>>>>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.
My point was that a work around the problem is possible. Technically you are certainly correct.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
