> Q1. I have tried to use the Filter Builder to return a string which later > can be > used to filter a table in a form? I can get this to work but how do I pass > the current filter string to the Foxfire Filter Builder so that user can > refine their previous filter? Everytime I called this Builder I have start > all over again. The whole point of Foxfire! is to hide the details of the RQBE, SELECT, etc. from the user. As I see it, you have two options: 1) redefine the filter using the Data Item names that Foxfire! understands 2) set up a Foxfire! request, and then override its SQL statement (there are tons of limitations with this, and usually few benefits). > Q2. When I called Foxfire Request Editor from my app. thru one of my > menu option, the window is not a modal form. Without closing this I choose > another report menu option which also called the above and it crashed. Is > there a way to prevent this? I've got a global variable, m.slFoxfire, set up as .F.. When I call Foxfire!, I set this to .T.. When Foxfire! ends, I set this back to .F.. I also have this variable in all of the menu SkipFor clauses. > Q4. I have encountered cosmetic problem when the SORT+GROUP command button > is clicked form the REQUEST EDITOR? You can see the screen behind the > window. How to overcome this? I've seen some strange things when using Foxfire!, and they're quite unlike anything else that I've seen FoxPro do on its own. I'm not sure what the solution to this particular one is, I just want to state that you're not alone with it. /Pau