It's VFP caching in action. If you issue loSession = XFRX("XFRX#INIT") in EXE first, VFP caches xfrx.fxp from EXE, otherwise it caches xfrx.fxp from APP. Any program (fxp) can only see reports from EXE/APP it's built into. I don't think there's a simple salutation to this problem.

>
>I have come across the following problem:
>
>The .EXE application calls an .APP project. The .APP project is using XFRX to convert a report to a PDF file. So far, it works.
>
>But after calling .APP, the EXE application that is also using XFRX always display a message the .FRX file not found.
>
>I have traced the problem to the line
>
>

>loSession = XFRX("XFRX#INIT")
>

>
>in the .APP application. That is, after this line, the EXE application XFRX cannot find .FRX file.
>
>The .APP application is converting .FRX residing on the disk and the EXE is converting .FRX in the .EXE file. Could this be the problem?
>
>How can I reset the XFRX to look for .FRX file in the .EXE instead of on the driver?
>
>Thank you in advance for any suggestions.
>
>UPDATE: I found out that a way to make the program work is to call XFRX in .EXE first. Then, if I call XFRX in the .APP and then back in the .EXE, everything works. So it seems like XFRX is initialized or does something first time (even though I use all local variables) that stays in the memory. Unless I am confusing something.