>Hello all,
>
>I *thought* I had it down where I presented the cursor fields in the expression builder when allowing the user MODIFY REPORT from an application (did so by hacking the FRX and adding a data environment). The user kept complaining they couldn't see the fields. Turns out it works great when I tested it in interactive mode, but when I compiled the app to an EXE, it does not work.
>
>Anybody run into this problem before?

My trick was to have no DE in the report, and have my own .prg for _GetExpr variable. When the expression builder was called, it would switch to the previous data session, set _getexpr="", call the usual expression builder, switch back to whichever data session was in effect. I've written a couple of these over the last couple of years, but they differed from app to app. I've even had one which pulled fields from SQL-side tables.