Datasheet

RAIS 3.0 Programmer’s Guide – Part I : Advanced Customization

here, please create a new preselection list query for the form [Evaluator Waste Management]

(see section 2.5).

To test that our evaluator is working, please create the following query and execute it.

Select * from [Facility] where [Facility].[PK Facility ID] in (select [Evaluator Waste

Management].[FK Facility ID] from [Evaluator Waste Management])

Now consolidate your backend with any other backend. Open the destination backend and

check the record of the waste management facility. Its primary key hopefully does differ from

the primary key in the source database, and you will notice that above query still produced

the correct result.

The new evaluator we have been creating appears in the Regulatory System menu, evaluators

defined in the standard version of RAIS 3.0 are not displayed; they are hidden. This hiding

feature has been introduced because it might be dangerous to modify, or even delete

evaluator records.

After we have defined and validated our new evaluator, we should also protect this evaluator

by hiding it from the Regulatory System menu. Open the table Treeview in the RAIS back-

end. Search for the record having the field value [Evaluator Waste Management] in the field

[PDI]. Lookup the associated value of the field [Key]; it will usually be something starting

with the letter M. This letter makes the menu node for our protector appear under the menu

group Common Tables. A hidden menu group exists in RAIS for hiding all evaluators,

having the key prefix X. Rename the key of the new protector to something like X99,

meanwhile taking care that this key is not yet used.

2.2.2 Comments

We have defined the protector for protecting the waste management facility to be called

[Protector Facility]. We did not call the evaluator for the waste management facility

[Evaluator Facility], but we gave it name [Evaluator Waste Management]. This evaluator

shall not be used for any other purpose than retrieving waste management facilities. If more

than one record is appended to this evaluator, we must take care that queries – using this

evaluator – do not produce unintended duplicate records.

Another example of an evaluator that contains IDs of sources that are considered to be “in”

is shown in the picture below . As it is seen, query and statistics results depend very much on

evaluators, 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 evaluators for possible

resolution.

As it is seen, query and statistics results depend very much on evaluators, 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 evaluators for possible resolution.