Chapter 7 - Search for Documents - Revision history

SSprencel at 20:40, 20 April 2011

2011-04-20T20:40:22Z

SSprencel: /* Starter Searches */

2010-03-24T18:07:09Z

‎Starter Searches

SSprencel: /* Setting Up Custom Search Features */

2010-03-24T18:03:23Z

‎Setting Up Custom Search Features

SSprencel: /* Managing Search Windows */

2010-03-24T17:59:48Z

‎Managing Search Windows

SSprencel: /* Imaging View Window */

2010-03-24T17:58:42Z

‎Imaging View Window

SSprencel: /* Criteria Field Types */

2010-03-24T17:57:52Z

‎Criteria Field Types

SSprencel: /* Search Menu Summary */

2010-03-24T17:56:07Z

‎Search Menu Summary

Show changes

SSprencel: /* Starter Searches */

2010-03-24T15:49:55Z

‎Starter Searches

SSprencel: /* Soundex Searches */

2010-03-24T15:41:54Z

‎Soundex Searches

SSprencel: /* Creating the SmartNames table */

2010-03-24T15:41:02Z

‎Creating the SmartNames table

@@ Line 19: / Line 19: @@
 ===The Search Criteria Window===
 When the search feature is loaded, a screen similar to the following is displayed:
@@ Line 118: / Line 120: @@
 ===Criteria Field Types===
 As you fill in the criteria fields, check the search type button box in the upper right hand corner of the criteria window to ensure that the desired search type is being performed. Search types include:
@@ Line 160: / Line 164: @@
 ===The Hit List Window===
 Once a search is performed, a hit list window similar to the sample below is displayed showing the results of the search. This grid includes a row for each record found in the search and a column for each field in the database. If a field is a multi-entry field, only the first entry in the database is displayed.
@@ Line 210: / Line 216: @@
 ===The Document Information Window===
 Once the Document Information Window is loaded the screen will be similar to the sample below. Fields that cannot be altered such as document number, storage location and folder appear in a lighter shade. These fields are used to locate the image relating to the document. Date fields are formatted using the long date format set up in the Windows Control Panel (Regional and Language Options). Multi-entry fields are placed in larger text boxes with scroll bars on the right if all the entries will not fit in the box. Like Index, a question mark icon will appear if a field is validated in a table.
@@ Line 228: / Line 236: @@
 ===Imaging View Window===
 If the document is an image, the Image View Window shown below is used to view the image. This View Window will automatically display when the Document Information Window is displayed.
@@ Line 283: / Line 293: @@
 ===Managing Search Windows===
 As described above, there are several windows that comprise the Search Module. By managing these windows, you are able to view the data and related images in many different ways. halFILE defaults to certain window sizes and formats and loads and hides the different windows automatically whenever they are needed. You can adjust the size and position of these windows and halFILE will remember the layout. halFILE also provides a Window menu to help you navigate between the various search windows.
@@ Line 327: / Line 339: @@
 ===Setting Up Custom Search Features===
 Use the '''Tools-Options''' menu in Index to define custom features that affect the Search Module. Unless otherwise explicitly stated, saving options here will affect all halFILE stations and users. The Tools-Options menu brings up a form that includes tabs for the following items:
@@ Line 475: / Line 489: @@
 ===SmartName Search===
 The SmartName search provides a way to key in a name as a search criteria and have the system generate common or nick names to search for. For instance, you can set up this feature to search for 'Richard,' 'Rich,' 'Dick,' 'Rick' and 'Ricky' when you entered 'Richard' for the search criteria. This also works for last names and company names.
@@ Line 542: / Line 558: @@
 ===Soundex Searches===
 Soundex is a search method that uses an algorithm to find data that 'sounds like' the search criteria you entered. This is typically used for name searches. While the soundex algorithm will often find names that are quite different from the name you are searching for, it is useful in many situations.
@@ Line 566: / Line 584: @@
 ===Cross Name Search===
 Cross name search is a feature where you can instruct the search engine to search two multi-entry text fields for a value, performing a single search for both fields. This is typically used against name fields. For example, if you have one field called First_Party and a second field called Second_Party, with this feature you can perform a search for 'Smith, John' and the system will search for any documents where the Grantor = Smith, John OR the Grantee = Smith, John.
@@ Line 583: / Line 603: @@
 ===Starter Searches===
 The Starter System was designed for the Title Industry but may have valuable application in other types of organizations as well. With this system, you define "criteria sets" consisting of fields which are commonly searched. Then, you can fill in all of the criteria for these sets and the system can perform a search using the criteria for each set to derive a composite search.
@@ Line 712: / Line 734: @@
 ===Proximity Search===
 "Proximity Search"  is a powerful new feature of the halFILE Search Module utilizing full text indexes. A full text search is performed, in which the words entered into the criteria must all be present but do not need to be in the same order as keyed. New full text indexes can be added to selected halFILE data fields like names, Grantors, Grantees, Addresses, etc. "Proximity" means each word in the search criteria for a field is in the same proximity in the database field. This feature requires SQL Server 2000 or later.
@@ Line 744: / Line 768: @@
 ===Full-Text Search===
 A new Add-On Product called Automated Indexing is available which can be used to build a full-text index on the entire document. The module converts TIFF images to words using OCR then loads the words into the full-text index. Other document types such as Word, Excel, and PDF can also be full-text indexed.
@@ Line 751: / Line 777: @@
 ===Search Menu Summary===

@@ Line 592: / Line 592: @@
 The Starter tab of the Tools-Options menu of the Search Module is used to configure options for halFILE's Starter system. These options are saved to hfstarter.ini. Note that for e.halFILE, these options are placed in halweb.ini. The following describes the settings.
-'''Enable this feature''' - check this box to enable the Starter system.<br />
+<u>'''Enable this feature'''</u> - check this box to enable the Starter system.<br />
-'''Database name contains the latest posted date in the last 10 characters''' - this option tells the system that the posted or plant date through which the database has been verified can be found in the last 10 characters of the database name (File-Databases-ODBC Info button of the Administrator). For example, "Jackson County thru 10/15/2004" would be an example where this option is valid.<br />
+<u>'''Database name contains the latest posted date in the last 10 characters'''</u> - this option tells the system that the posted or plant date through which the database has been verified can be found in the last 10 characters of the database name (File-Databases-ODBC Info button of the Administrator). For example, "Jackson County thru 10/15/2004" would be an example where this option is valid.<br />
-'''Starter Number Field''' - the Starter Number is the number under which the Starter criteria information is stored in the halFILE database. Select a field in which to store this information. Typically a file number field is used. The Starter Number is entered by the user setting up the Starter.<br />
+<u>'''Starter Number Field'''</u> - the Starter Number is the number under which the Starter criteria information is stored in the halFILE database. Select a field in which to store this information. Typically a file number field is used. The Starter Number is entered by the user setting up the Starter.<br />
-'''Starter Description Field''' - select the field where the description of the search is stored. The description is entered by the user setting up the Starter. This could be a remarks or comments field.<br />
+<u>'''Starter Description Field'''</u> - select the field where the description of the search is stored. The description is entered by the user setting up the Starter. This could be a remarks or comments field.<br />
-'''Open Date Field''' - select a date field where the date the starter was created is stored.<br />
+<u>'''Open Date Field'''</u> - select a date field where the date the starter was created is stored.<br />
-'''Close Date Field''' - once the starter search is no longer active, it can be closed. Select the date field where the date the starter was closed is stored.<br />
+<u>'''Close Date Field'''</u> - once the starter search is no longer active, it can be closed. Select the date field where the date the starter was closed is stored.<br />
-'''Starter Status Field''' - the Starter system posts an "open" status to the starter record when the starter is created and a "closed" status when it is closed. Select the field to be used to hold the status of the Starter. This is normally a document or instrument type field.<br />
+<u>'''Starter Status Field'''</u> - the Starter system posts an "open" status to the starter record when the starter is created and a "closed" status when it is closed. Select the field to be used to hold the status of the Starter. This is normally a document or instrument type field.<br />
-'''Fallout Date Field''' - this identifies the date to be used for the date down searches. Each time a search is performed for a starter, the date of the search is recorded in this field and becomes the beginning date for subsequent searches using this starter.<br />
+<u>'''Fallout Date Field'''</u> - this identifies the date to be used for the date down searches. Each time a search is performed for a starter, the date of the search is recorded in this field and becomes the beginning date for subsequent searches using this starter.<br />
-'''Security Group Field''' - in cases where multiple users are creating starters and you wish to configure the system so each user can see only the starter that he/she create, you can post this users security group (Configure-User Groups in the halFILE Administrator). If you select a field for storing the Security Group, then the group the user is in is stored in this field when the starter is created. You should then configure the User Group security to prohibit the viewing of Starter documents containing some other group value.<br />
+<u>'''Security Group Field'''</u> - in cases where multiple users are creating starters and you wish to configure the system so each user can see only the starter that he/she create, you can post this users security group (Configure-User Groups in the halFILE Administrator). If you select a field for storing the Security Group, then the group the user is in is stored in this field when the starter is created. You should then configure the User Group security to prohibit the viewing of Starter documents containing some other group value.<br />
-'''Open Status Value''' - the value to post to the Starter Status field when a starter is created. For example, "STRO" could be the code used for Open Starter.<br />
+<u>'''Open Status Value'''</u> - the value to post to the Starter Status field when a starter is created. For example, "STRO" could be the code used for Open Starter.<br />
-'''Closed Status Value''' - the value to post to the Starter Status field when a starter is closed. For example, "STRC" could be the code used for Closed Starter.<br />
+<u>'''Closed Status Value'''</u> - the value to post to the Starter Status field when a starter is closed. For example, "STRC" could be the code used for Closed Starter.<br />
-'''New Document Prefix Letter''' - Enter a one character prefix letter to be used when create the starter document record in the halFILE database. Try to configure a unique letter not used by as a Station Id on capture stations.<br />
+<u>'''New Document Prefix Letter'''</u> - Enter a one character prefix letter to be used when create the starter document record in the halFILE database. Try to configure a unique letter not used by as a Station Id on capture stations.<br />
-'''Starter Basket''' - enter the basket name to be used for newly created starter documents. This must be a valid basket name. We recommend a basket named "Starter."
+<u>'''Starter Basket'''</u> - enter the basket name to be used for newly created starter documents. This must be a valid basket name. We recommend a basket named "Starter."
@@ Line 619: / Line 619: @@
 To set up a criteria set, select the set number from the Criteria Set drop down box, configure all the options, then click '''Save Set'''.
-'''Set Description''' - describes the search for this criteria set. Normally, it would be similar to the field selected in the Field to search box.<br />
+<u>'''Set Description'''</u> - describes the search for this criteria set. Normally, it would be similar to the field selected in the Field to search box.<br />
-'''Field to search''' - select the field to search when the starter search for this criteria set is performed.<br />
+<u>'''Field to search'''</u> - select the field to search when the starter search for this criteria set is performed.<br />
-'''Order hit list by''' - enter the order by clause to use when the starter search for this criteria set is performed. The default button selects an order by using the field selected in the Starter Number field box. This must use valid SQL statement form and the field names used must be valid to prevent an error from occurring when a search is performed.<br />
+<u>'''Order hit list by'''</u> - enter the order by clause to use when the starter search for this criteria set is performed. The default button selects an order by using the field selected in the Starter Number field box. This must use valid SQL statement form and the field names used must be valid to prevent an error from occurring when a search is performed.<br />
-'''Default search type''' - select the default type of search to perform for this criteria set. The following are our recommendations for the common starter criteria sets.<br />
+<u>'''Default search type'''</u> - select the default type of search to perform for this criteria set. The following are our recommendations for the common starter criteria sets.<br />
 * Grantor - BEGIN
 * Grantee - BEGIN
@@ Line 694: / Line 694: @@
 The Fallout Report tab of the Tools-Options menu configures the options used to print the report. The report must be built using Crystal Reports (a sample report, fallout.rpt, is provided). Also, your fallout report program, HFFallout.exe, must match the Crystal Reports version.
-'''Fallout Report Description''' - describes the report.<br />
+<u>'''Fallout Report Description'''</u> - describes the report.<br />
-'''Fallout Report Path''' - the path where the Crystal Report is located.<br />
+<u>'''Fallout Report Path'''</u> - the path where the Crystal Report is located.<br />
-'''Fallout Report File''' - the file name of the Crystal Report. Do not enter any path information, just the report file name.<br />
+<u>'''Fallout Report File'''</u> - the file name of the Crystal Report. Do not enter any path information, just the report file name.<br />
-'''Last Fallout Report Date''' - this shows the date the report was last run. This date will be used as the starting date for the next Fallout Report process.
+<u>'''Last Fallout Report Date'''</u> - this shows the date the report was last run. This date will be used as the starting date for the next Fallout Report process.
 The Fallout report can be run interactively or in auto mode. To run the report interactively, select the '''Starter-Fallout Report''' menu on the Search Criteria window. The date range is automatically filled in from the last time the report was run. The available fallout reports are listed in a drop down box. Select the report to run and click the '''Run Report''' button. Once report processing is complete, a message is displayed. Then click the '''Print Report''' to print the report results.

@@ Line 334: / Line 334: @@
 The Hit List tab is used to set up special halFILE features pertaining to the Hit List window including:
-'''Hit List Descriptions''' – For coded validation fields, this option can be checked to show the table description instead of code on the hit list. Note that when this option is enabled, then the description is displayed for every coded field except TitleSubdivision and TitleTownship.
+<u>'''Hit List Descriptions'''</u> – For coded validation fields, this option can be checked to show the table description instead of code on the hit list. Note that when this option is enabled, then the description is displayed for every coded field except TitleSubdivision and TitleTownship.
-'''Display Results''' – this defines how the search results are listed on the Hit List Window. The options are:
+<u>'''Display Results'''</u> – this defines how the search results are listed on the Hit List Window. The options are:
 * One row per document – this is the traditional halFILE hit list format where one row per matching document is shown and the data shown is from the first multi-entry row of the document.
 * Rows that match the criteria – this option will display multi-entry data from the row that matched the criteria. For example, if you performed a search for a name = "Smith" and on the document the Names were listed as "Jones, Bob" then "Smith, Mary" then "Smith, John," then the Search hit list will show a wide row with "Smith, Mary" and Smith, John" listed since they matched the search criteria.
 * All rows (includes multi-entry) – this options displays all rows for documents match the search criteria. In the above example, "Jones, Bob" then "Smith, Mary" then "Smith, John" are listed.
-'''Hit List Button Execute''' – this section configures a user-defined button at the bottom of the hit list. A template is provided for the Pending Order system where a button is set up to define a new Pending Order.  A second template is available for setting up the Word Merge feature where the results of the search can be filtered through a Word Merge document.
+<u>'''Hit List Button Execute'''</u> – this section configures a user-defined button at the bottom of the hit list. A template is provided for the Pending Order system where a button is set up to define a new Pending Order.  A second template is available for setting up the Word Merge feature where the results of the search can be filtered through a Word Merge document.
-'''References'''– this section defines the halFILE Reference feature handling in Search. The Reference feature, set up in the database section of the halFILE Administrator, is used to reference one halFILE document to another by linking data in two or more fields. On this screen, you define whether the View References box on the Search Criteria page should be checked by default when entering the search module. You can also set up the colors to use for any Reference documents added to the Hit List.
+<u>'''References'''</u>– this section defines the halFILE Reference feature handling in Search. The Reference feature, set up in the database section of the halFILE Administrator, is used to reference one halFILE document to another by linking data in two or more fields. On this screen, you define whether the View References box on the Search Criteria page should be checked by default when entering the search module. You can also set up the colors to use for any Reference documents added to the Hit List.
-'''Hit List Colors''' – this section defines the Hit List color coding for selected documents. Here, you set up the colors to use for documents that match a certain criteria. For example, you can set this up so documents that have the code 'WD' in a Doc_Type field show up as white on blue. This makes important documents stand out. When setting up these color settings, you first select a Color Set. This are numbered sets beginning with one. halFILE does not allow gaps in the color sets used (i.e. if you set up color set 1 and color set 3, and color set 2 is blank, then color set 3 will be ignored.) After selecting the color set, you should select the Field to match, enter the data to match, and chose the foreground and background colors by clicking the '''select''' buttons.. When the colors are selected, you will see words "Sample Text" changed to reflect the selected color. Once the color set is defined, click the '''Save Color Set''' button to save the parameters.
+<u>'''Hit List Colors'''</u> – this section defines the Hit List color coding for selected documents. Here, you set up the colors to use for documents that match a certain criteria. For example, you can set this up so documents that have the code 'WD' in a Doc_Type field show up as white on blue. This makes important documents stand out. When setting up these color settings, you first select a Color Set. This are numbered sets beginning with one. halFILE does not allow gaps in the color sets used (i.e. if you set up color set 1 and color set 3, and color set 2 is blank, then color set 3 will be ignored.) After selecting the color set, you should select the Field to match, enter the data to match, and chose the foreground and background colors by clicking the '''select''' buttons.. When the colors are selected, you will see words "Sample Text" changed to reflect the selected color. Once the color set is defined, click the '''Save Color Set''' button to save the parameters.
 As an example of two the Hit List Color preferences should be set up, let's set it up so the Hit List row is white on blue if the Doc_Type field is 'WD,' white on red if the Doc_Type field is 'NTG' and black on pale yellow for all other rows. Here is the process:
@@ Line 424: / Line 424: @@
 The Lost Focus Execute trigger defines an external program that is run when information in a field on the Document Information window is changed.  This feature lets you restrict the triggered program to run only when the designated field is modified.
-The Search Execute trigger is run when a document is saved in search. A common example of when this option is used is the Pending Order System feature where, after a document is saved, the pending order program is run to check to see if any of the data being posted may affect an open order. A template button is available on this form to provide a sample of a pending order check. Another template is provided for running the HFFlow32.exe which synchronizes data in two halFILE databases that are involved with database lookups to each other. When this option is saved, the setting is written to the database section \[aaaHFWdd\] of halfile.ini and therefore affects saving document information on all station.
+The Search Execute trigger is run when a document is saved in search. A common example of when this option is used is the Pending Order System feature where, after a document is saved, the pending order program is run to check to see if any of the data being posted may affect an open order. A template button is available on this form to provide a sample of a pending order check. Another template is provided for running the HFFlow32.exe which synchronizes data in two halFILE databases that are involved with database lookups to each other. When this option is saved, the setting is written to the database section [aaaHFWdd] of halfile.ini and therefore affects saving document information on all station.
@@ Line 451: / Line 451: @@
 This frame configures Word Merge options that affect all stations. These settings are written to the wordmrg.ini file.
-'''Unique database field''' - select a field which can be used as a unique key to the Word Merge database. The contents of this field can occur only one time in the hit list. Typically this is a file number of some type.<br />
+<u>'''Unique database field'''</u> - select a field which can be used as a unique key to the Word Merge database. The contents of this field can occur only one time in the hit list. Typically this is a file number of some type.<br />
-'''Date format''' - select the date format to use when writing dates to the Word Merge database file.<br />
+<u>'''Date format'''</u> - select the date format to use when writing dates to the Word Merge database file.<br />
-'''Post table description''' - For coded fields, check this box if you wish to write the description from the code table instead of the code.<br />
+<u>'''Post table description'''</u> - For coded fields, check this box if you wish to write the description from the code table instead of the code.<br />
-'''Combine multi-entry information as one record''' - check this box to write one record per document to the Word Merge database, combining multiple entries.
+<u>'''Combine multi-entry information as one record'''</u> - check this box to write one record per document to the Word Merge database, combining multiple entries.
@@ Line 461: / Line 461: @@
 This frame configures Word Merge options that affect this station only. These settings are written to the wordmrgl.ini file in the Windows folder.
-'''Program to run for Word Merge''' - select the Word executable file, normally Winword.exe.<br />
+<u>'''Program to run for Word Merge'''</u> - select the Word executable file, normally Winword.exe.<br />
-'''Word merge database path''' - select the path where the Word Merge database is saved.
+<u>'''Word merge database path'''</u> - select the path where the Word Merge database is saved.

@@ Line 305: / Line 305: @@
 When you click the Begin Search button to perform a search and the system detects that there are already documents in your Search Hit List, a pop up menu will give you append search options that you can perform as follows:
-'''Search primary and add to hit list''' - this option will search your document database and add any new records found that match the criteria to the existing records in your hit list.
+<u>'''Search primary and add to hit list'''</u> - this option will search your document database and add any new records found that match the criteria to the existing records in your hit list.
-'''Search hit list and retain matches''' - this is a sub-search of the records found in your hit list. Any records that found match the criteria are kept in the hit list while those records that do not match the criteria are discarded.
+<u>'''Search hit list and retain matches'''</u> - this is a sub-search of the records found in your hit list. Any records that found match the criteria are kept in the hit list while those records that do not match the criteria are discarded.
-'''Search hit list and delete matches''' - this also performs a sub-search of the records in the search hit list. Any records found meeting the criteria are removed from the hit list.
+<u>'''Search hit list and delete matches'''</u> - this also performs a sub-search of the records in the search hit list. Any records found meeting the criteria are removed from the hit list.
-'''Clear hit list and begin new search''' - this selection clears any existing records from the search hit list and begins a new search of your document database using the criteria.
+<u>'''Clear hit list and begin new search'''</u> - this selection clears any existing records from the search hit list and begins a new search of your document database using the criteria.

@@ Line 274: / Line 274: @@
 |Alt-4||zoom to lower right quadrant
 |-
-|Alt-\~||Fit width (toggles upper half/lower half of document)
+|Alt-~||Fit width (toggles upper half/lower half of document)
 |-
 |Ctrl-F||Goes to first page of the document

@@ Line 120: / Line 120: @@
 As you fill in the criteria fields, check the search type button box in the upper right hand corner of the criteria window to ensure that the desired search type is being performed. Search types include:
-'''Exact Match''' - the field data in the database must exactly match the criteria.<br />
+<u>'''Exact Match'''</u> - the field data in the database must exactly match the criteria.<br />
-'''Beginning of Field''' - the field data in the database must begin with the criteria entered.<br />
+<u>'''Beginning of Field'''</u> - the field data in the database must begin with the criteria entered.<br />
-'''End of Field''' - the field data in the database must end with the criteria entered.<br />
+<u>'''End of Field'''</u> - the field data in the database must end with the criteria entered.<br />
-'''Free Form Search''' - the field data in the database must contain the criteria entered.
+<u>'''Free Form Search'''</u> - the field data in the database must contain the criteria entered.
 ----
@@ Line 131: / Line 131: @@
 ----
-'''Greater Than''' - the field data in the database must be greater than the criteria entered.<br />
+<u>'''Greater Than'''</u> - the field data in the database must be greater than the criteria entered.<br />
-'''Less Than''' - the field data in the database must be less than the criteria entered<br />
+<u>'''Less Than'''</u> - the field data in the database must be less than the criteria entered<br />
-'''Range''' - the field data in the database must be within the range of the two criteria values entered.<br />
+<u>'''Range'''</u> - the field data in the database must be within the range of the two criteria values entered.<br />
-'''SmartName Search''' – when you exit from a criteria box designated as a Smart Name search, the system converted the names in the box to aliases using the Smart Name dictionary. See Smart Names for more information.<br />
+<u>'''SmartName Search'''</u> – when you exit from a criteria box designated as a Smart Name search, the system converted the names in the box to aliases using the Smart Name dictionary. See Smart Names for more information.<br />
-'''Soundex''' – a "sounds like" search is performed on the criteria field.<br />
+<u>'''Soundex'''</u> – a "sounds like" search is performed on the criteria field.<br />

@@ Line 648: / Line 648: @@
 [[Image:Starter_Search_Overview.jpg]]
-The '''Save? '''column on the left indicates which fields you want to save to the Order. Normally, you would leave all items set to yes as is the default but they come in handy when you want to update the criteria for an order. To toggle the yes/no double click the cell. Also, at the bottom of the grid you will find the date range to search. The beginning date on a new order is preset at 1/1/1900. The ending date is either today's date or if configured, the system can pull the ending date from the database name. For example, if you maintain the database verification date in the database name, as the last characters of the name, the system can strip it off the name. Either way, if the "save ending date for date down search" check box is checked, then the ending date is saved to the order so it will be available for "date down" searches at a later time. Finally, there is a "view references" check box at the bottom. If this is checked, the reference documents will be included in the search.<br />
+The '''Save? '''column on the left indicates which fields you want to save to the Order. Normally, you would leave all items set to yes as is the default but they come in handy when you want to update the criteria for an order. To toggle the yes/no double click the cell. Also, at the bottom of the grid you will find the date range to search. The beginning date on a new order is preset at 1/1/1900. The ending date is either today's date or if configured, the system can pull the ending date from the database name. For example, if you maintain the database verification date in the database name, as the last characters of the name, the system can strip it off the name. Either way, if the "save ending date for date down search" check box is checked, then the ending date is saved to the order so it will be available for "date down" searches at a later time. Finally, there is a "view references" check box at the bottom. If this is checked, the reference documents will be included in the search.
-The '''Save Starter Information''' button saves the Starter information under the order number you provided. The information is stored in the halFILE database and is given a document type of "Starter" as defined in the parameters. The criteria set information is also stored in the related database fields in the database.<br />
 The '''Save Starter and Run Search''' button saves the starter information, and then performs a "starter search". A search is performed for each criteria set and a composite hit list is displayed as shown below. If you want to perform the search but do not care to save the starter information to the database, click the '''Run Search (nothing saved) '''button.
@@ Line 707: / Line 709: @@
 To save the ending date as the new starting date for the Fallout Report, click the '''Save New Fallout Date''' menu.
 Since the Fallout Report processes every Open Starter, it is important to close your starters when they are complete.
 ===Proximity Search===

@@ Line 563: / Line 563: @@
 '''Limitations to Soundex'''
-Soundex can only be used on database engines that support the SQL Soundex function. This function is <u><u>NOT</u></u> supported in Microsoft Access at this time so the Soundex button is disabled in search if your database is Access. The soundex function is valid in other databases such as Microsoft SQL Server and Sybase SQL.
+Soundex can only be used on database engines that support the SQL Soundex function. This function is <u>NOT</u> supported in Microsoft Access at this time so the Soundex button is disabled in search if your database is Access. The soundex function is valid in other databases such as Microsoft SQL Server and Sybase SQL.
 ===Cross Name Search===

@@ Line 500: / Line 500: @@
 # Click '''add proper name'''.
 # Enter the proper name (i.e. Richard) in the proper name box.
-# Enter any variations on spelling as well as nick names for the proper name in the alias names box. Please be sure to hit enter between each alias name you enter. (i.e. Rich \[enter\] Dick \[enter\] Richie).
+# Enter any variations on spelling as well as nick names for the proper name in the alias names box. Please be sure to hit enter between each alias name you enter. (i.e. Rich [enter] Dick [enter] Richie).
 # Click OK.
@@ Line 515: / Line 515: @@
 # Click '''delete proper name.'''
 # Click yes to remove the proper name and all of its nick names from the list.
 ====Searching for a proper name====