Datasheet

RAIS 3.0 Programmer’s Guide – Part I : Advanced Customization
16
As it is seen, query and statistics results depend very much on evaluators. For example, a
query default query shows all sources in the country using the evaluator from the example
above, depends on it very much. If a new status for source would be added by user in setup,
this query may show incorrect results as new status is not considered by the evaluator.
Therefore if any query is not producing the desired result (omitting certain type of records, or
vise versa, showing irrelevant records), one should turn to corresponding evaluators for
possible resolution.
2.3 Creating Custom Consistency Checks
Consistency checks are fired upon saving records, either after appending a new record or
updating a modified record within an input form. Consistency checks are regular SQL
statements, returning rows of records. A consistency check is considered non successful if no
record row is returned, else the consistency check is considered to be successful. If the
consistency check is not successful (evaluates to FALSE) an appropriate message is
displayed. This message only is a warning message, users are allowed to skip this message
and continue saving the record.
As consistency checks are fired upon saving records, they need to evaluate data users have
entered into fields on the input forms before the record is stored. Fields in input forms may
easily be evaluated within SQL expression by statements as for example
Forms("Input").Controls("ChildForm").Controls("Details").Controls(“Serial No”)
to retrieve the value entered in the field [Serial Number] of a generator or sealed source. To
find out the field name of a form field, open the form in design mode and have a look at the
property “Name” in the form designer of Microsoft Access. To find the name of the form to