
As the size and scope of a database grows, finding specific information can become difficult. Large amounts of data become confusing and awkward to manipulate. It is critical that users be able to limit the amount of data under consideration so that they don't become overwhelmed by vast data sets. System considerations also favor smaller data sets to improve response times and stability.
Filters give users the ability to set criteria by which data sets may be reduced in size to include only relevant information. Filter settings can be made and adjusted in a natural and intuitive manner, easily changed by the user and stored locally between editing sessions.
An example of a filtering operation might be to take all of the names in a phone book and select only those whose last name is "Smith". This will produce a data set far smaller than all of the names in the phone book. The filter could be refined by including the additional requirement that the first name start with the letter "J". This will produce an even smaller data set from which the specific phone number of John Smith might be found.
In the example filter screen above, the settings will return a data set for the line items on sales orders for the customer Widgets of Wichita written after April 1, 2004 that are for item code 12345.
Another common use of data filters is to analyze time periods of data for summary information. For example you might compare sales data from a month long period for last year versus this year. To do this, you would run the filter twice, once with last years settings, then again with this year.
It is important to note that the system will include the date of the setting in the data. In the example above, this implies that orders written on the First of April will be included in the returned data. Likewise, the before date setting will include data written on that date as well. If you wanted all of the orders written in April, 2004, the after date would be 4/1/04 and the before date would be 4/30/04.
The example above shows a star used to allow any characters in the order field at the beginning, requiring that the last character be a 3. This filter will return order numbers 00003, 00013, 00023, etc. You can use this technique to avoid typing in preceding zeros when looking for a specific order number
Multiple stars may be used in a field search. In the example above, any code with the string sequence 2345 will be return in the result set. This would include 12345, 22345, 23456, etc.
This check box can be found at the bottom of the right hand side of most main screen panels.
The beauty of attributes is that you can arbitrarily extend their functionality by adding more values. For example, you might have an approval process that requires a manager to review the order before it may be submitted for fulfilment. In this case, you could add an Approved status for orders accepted.
Adding values to attribute sets is somewhat different than other cross table fields. You can add from the selection box of an attribute field on a particular data item by using the Add button. Alternatively, you can work with attribute values from the spreadsheet of the data by using the "Attrib" button.