Hi Richard;

  FYI: The DWO's "Query Mode" will only work with its own internally built SQL or an assigned View. In either of those two cases, the DWO can have access to the full SQL "Select" statement. Then once its sees the Query Criteria, it can then manipulate its SQL accordingly. In the case of an SP based DWO - the DWO does not see any SQL. Just a call to a remote DB object with some optional parameters.

  FWIW: If you intend on using the SP as the DWO's data source, I would write your own PowerScript to introspect the DWO's state after taking out of Query mode and then apply the appropriate "Where" criteria changes to the SP calling parameter list as required. The other alternative would be to capture your own criteria in a custom dialogue  and then use that to fire the SP based DWO with the appropriate parameters.

     The last alternative would be to have two DWO's - one for normal SP use and one for Query Mode and swap out the SP DWO for the SQL based DWO when doing Query Mode operations and then just let the SQL based DWO handle the DB Query from the PB client side.

Food for thought.

HTH

Regards ... Chris