Page History

...

HullForm$ is determined by means of a relation:

HULLDATA# is HULLDATA# is the selected input set for the calculation and is defined by an |OPTIONS| script represented as a Telitab set in its data slot of the parameter:

...

The script between |OPTIONS|….| describes how, what and where to get the Telitab set you will refer to as HULLDATA#as HULLDATA#.

This particular script describes three selection steps through a dataset, 
"Ship type" (represented by the data connected to parameter SHIPTYPE$), 
"Order number" (represented by the data connected to parameter PROJECT$) and 
"Loading condition" (represented by the data connected to parameter CONDITION$).

...

Please realise that the last item, "DATA#" "ParentShips", defines the reference for HULLDATA# to for HULLDATA# to the actual total data set. This is the data set for the selection as described by the script. In this case the data is available in the ParentShips object.

...

The line "HullForm$" "" in the script tells the system that at least a DETERMINED value of HullForm$ should be available to allow selection of a case. This means, that the result of the selection cannot be empty values for HullForm$, therefor Quaestor will pre-filter all these cases out of the total dataset. The selection of HULLDATA# will of HULLDATA# will contain all other DETERMINEDvalues available in the selected record. Also SHIPTYPE$, PROJECT$ and CONDITION$ should be DETERMINED (thus available) to allow a selection.

...

By using the QUERY# function with this syntax: QUERY#(0, Arg_1$[:ParLab_1$],,,,Arg_n$[:ParLab_n$]) for HULLDATA# for HULLDATA#, you can make sure that already available parameters will be used to pre-filted the options.

For instance when the ship type is already defined earlier in the solution, or is available as starting data in the dataset, you can add the relation HULLDATA# = QUERY#(0, SHIPTYPE$) to make sure that OPTION1 already uses the value for SHIPTYPE$.

...