On the following screen, choose the Field name to generate the Scalar Frequency Table for, and select the
Override Scalar Frequency Table
option.
Click
OK
, the following screen is shown:
Enter the file name that contains the names, or if overriding the Address_Part1 field, the file that contains the address data up to, but not including, locality/state/postcode information. If the data is stored in Unicode, choose the appropriate Unicode encoding.
If the file contains the relevant data in a certain column, enter the appropriate field offset and field length.
Maximum Keys defines the maximum number of entries in the table. If this field is left as "0", all keys generated from the file of names will be used in descending frequency up until the value specified in Minimum Frequency is reached. A value other than "0" will cause the table to be truncated to that number of keys, in descending frequency. This allows some additional control over the size of the generated Local Population. However, if the size of the generated Local Population is not an issue, this value should be left as "0".
Minimum Frequency defines the frequency value above which keys will be added to the table. To choose a value for this setting, first establish the approximate size of the database of names that will be being searched in the production system, then determine the percentage of this file above which a search warning should be generated. For example, the production database contains 1,000,000 entries and the requirement is to receive a search warning if more than 500 candidates (0.05% of the file) are returned for a search.
Now, translate that 0.05% to the size of the input file to the Scalar Frequency Table generation process. So, for example, if there are 50,000 names in the input file, 0.05% is 25. Therefore, enter 25 as the Minimum Frequency.
Setting this value too low will increase the size of the Local Population significantly.