Users can also determine how the documents included in the search results will be sorted by using the Sort Results By drop-down list. This search feature provides the following sorting options in Table B.

Additionally, users also have the ability to construct their search (or qualify the search they've already entered) through the use of several predefined search conditions. These conditions (or one-screen wizards, as I like to think of them) can make the task of entering typical search criteria easier than using the Notes full text query syntax.

You can use as many search conditions as you like, and as often as you like in a search. For example, you can use the search conditions to restrict the documents returned to those that:

• were created or modified on a date or date range
• were created or modified by one or more author(s)
• contain a specific value in a field
• were created using a specific form
• contain or do not contain multiple words or phrases (up to eight)
• match the values entered into a sample form

Use of these search conditions in Notes/Domino applications is outside the scope of this article.

While all of this functionality is available to Notes client users at the click of a Toolbar button, this is not the case for users who access the same application with a browser. When you Web-enable a Notes database, you'll also need to make additional design changes so that browser users will be able to search it via the Web.

It's true a user can construct a URL that includes the desired search criteria and options, but how many users do you know would be willing to do that? In the sections that follow, I'll show you two ways to provide search functionality to browser users in a matter of minutes.

The simple method
The easiest way to add search functionality to a Domino application is to do the following:

• Create the full-text index
• Create a new shared action called Search
• Add the Search shared action to all user views