Omit

[Slobey]

Hi again,

I have a solution that I would like to hide the status area from my users to minimize any problems that may occur. My problem is that I would like them to be able to perform a find using the omit button. Is there some other place to do this. i have a find script but how do I place the option of omitting in it? or is there a keyboard stroke or is it anywhere else but in the status area? Thanks in advance.

[Slobey]

Hi again,

I have a solution that I would like to hide the status area from my users to minimize any problems that may occur. My problem is that I would like them to be able to perform a find using the omit button. Is there some other place to do this. i have a find script but how do I place the option of omitting in it? or is there a keyboard stroke or is it anywhere else but in the status area? Thanks in advance.

[Vaughan]

In Find mode, the "Omit Record/Request" script step is the equivilent of selecting the omit check box in the status area.

[Slobey]

Thanks for responding. I am not sure I understand. I know I can omit with a script if I know that is what they want. But how do I give the user the option of omitting, extending, or constraining by using my find button and no status area? Or should I post this in the scriptmaker forum?

[jhomer]

Im not sure if this is the best option, but you could create a button for each find execution a user may want to conduct. Attach a paramater to each button and then write the the script to execute a find based on the button selected.

[Fenton]

I don't know of any new 7 techniques for this. But there is an older technique. Which is to exploit the fact that a calculation field is empty in Find mode. It requires a dedicated Find layout, and a script.

If you have a Constant=1 field you can use that. Put it on the Find layout, formatted as checkbox with a Boolean value list, 1, labelled as "Omit".

The user checks it. When they click a button to perform the find, you loop through the requests. If your "omit" field (Constant in this case) has a 1, Omit Record/Request. When you've looked at all requests you perform the actual Find.

Not sure how this would work with Constrain and Extend. But if you use extra calculation fields to produce checkboxes for them on the layout, I don't see a great reason why your script couldn't perform the step. Not tried though.

[Slobey]

Thanks guys, It sounds like I should just let them have the status area. I appreciate your help

[Vaughan]

Yes... I now let users have the status area unless there is some other compelling reason no to, like needing to display layouts based on a field value. But then I'm also trying to avoid any sort of navigation system that requires something like this as well.