If you are scripting this, you need to be careful on WHERE the omits occur. All new requests can be in any order, except all Omit Record steps should be after the other requests.
I will have a global-field layout where things like this can be 'set' and then passed to a find script. Add a checkbox "omit" next to any request to omit, but remember each field would have this.
Might it be advantageous to teach your users how to use the manual finds which have wildcards, omits, constrain and extend (among other features)?
p.s. yes an "omit" button can be placed on a record to use (even if manual finds are used), rather than the menu items
That omit button would use the Omit Records script step. You can use get ( windowmode ) to keep the button from doing anything in Browse or even hide the button in Browse mode.
Mais oui! I use the Omit in Browse mode more than Find mode, so YMMV. Hey, Phil! I have not tested the manual finds with this Omit button (calling the script step) on each record. Do you think it cares where the omits occur?
1 of 1 people found this helpful
"Do you think it cares where the omits occur?"
The rules for manual and scripted finds are the same. Omit requests should come last when you have multiple requests. That's because they work on the found set produced by the other request(s). They are the original constrain found set operations.
2 of 2 people found this helpful
As others have already suggested (quite correctly), you can provide an "omit" button on your layout for the user to click while in Find mode.
Couple additional items might make this work better though. It's useful for users to be able to tell whether they've clicked the omit button or not. For example, user clicks Find button to enter find mode, in a list view.
Request 1: state="Texas"
Request 2: city="Dallas"
If user wants to omit Dallas, he/she can click on the omit button. But you need to give 'em feedback that the second request is now an omit request. The Get(RequestOmitState) function can be used to calculate the status of the request (is it an omit request or not) and display some sort of a flag as appropriate.