I think that approach works fine for reports, where there is only one query sent to the server, but a similar approach for the browse is much more difficult, because the view engine in several places will try and add rows to your queue using the original definition of the view, and not your PROP:SQL. Anywhere in the viewmanager class where it does a SET or RESET you need to make sure that it never reaches that point. I think I tried this at some point, but I don’t remember if I ever got it fully working.