Scripting a find -- (find vs. browse mode) ??

[Steven Cappiello]

I've tried to create an "Advanced Find" feature in my database that searches on 10 fields in my solution.

I've tried 2 methods...

1. The first is a 2 part script that enters the user into find mode for them to type their find criteria

part 1.. brings you to a search layout, then enters the person into Find Mode

part 2.. Triggered by a "Search" button..performs the find and if there are results, brings you to a results layout

the problem with this was that after part 1.. if the person hits "enter" it just completes the find

and the person is left with their results on the search layout!

If this is the best way to go, is there a way I can prevent the find from happening if the person presses enter or return ??

2. I created some global fields, and then bring the user to a layout that has the globals on it in browse mode. Then, a Search button performs a find and brings them to the results page if there are results.

One problem with this is that when they first are brought to the Search Layout, since there are a lot of records in this database, it takes a while for them to be able to type. The second problem is that user can't enter multiple find requests with this method.

Which method seems better for me ? and.. are there ways to avoid the problems with both methods ??

[-Queue-]

1. Have the first script Pause after it enters Find Mode, then call the Search script. Make your Search button a simple Resume Script, not a call to the Search script. Then, whether they click the button or press Enter/Return, the first script will continue.

2. A layout containing only globals shouldn't slow down the file at all. Are you sure there are only globals on it? Are you nullifying the globals at the start of the script and maybe that is what takes so long?

True about multiple find requests. You would need multiple layouts containing different globals or different repetitions of the same globals, or a script to set the first repetitions into the second repetitions, then nullify the first repetitions, or if the second reps were already used, set the third repetitions, etc. Clearing all of these at the beginning of the script would take even longer to perform. I think you would do better with such searches by using your first technique.