Ariadne index page

 

Ariadne - Technical description

A290

Assigning start numbers

Description

After the competition program is complete, and before the program is to be printed, the start number are assigned to the entries /competing units. The assignment of the start numbers is in order of event number and of ranking within the events. The assignment of start numbers is contiguous between events, e.g. no reservation of start numbers between events.

With the assignment of start numbers, a check is done that a competing unit has two run records (for two series).

The assigned start numbers originate from T050-Start-number. Start numbers in this table, marked as missing, are not assigned.

On activation of the form, a check is performed whether there are competing units which are not assigned yet to an event, and wheter there are categories which are assigned to more events (with exception of shadow events).

The start number assignment can begin from a start number as specified. (StartNumberOffset). In this way the start number assignment can begin with for instance start number 200. Further can be specified whether yes or no to overwrite earlier assigned start numbers. After automatical assignment of start numbers, the entry period is set to closed.

Function differentiation for the Downriver version

In the downriver version the start time is specified for each competing unit. There is a correspondence between the start number and the start time. The correspondence is that the unit number of the start minute is the same as the unit number of the start number. The assignment of start time / start number occurs per program block. In a program block the start number range is contiguous. Per program block the start time can be specified, plus the begin start number. Take care that the unit number of the start number corresponds with the unit number of the start time. E.g. start time of the block is 10:01, and the begin start number of the block is 21.

Also can be specified how many spare start numbers are to be reserved at the start of every event in the program block. If you want time blocks between events, you should assign these events to different program blocks.

Access path

F000-Menu  
F560-Assigning-start-numbers  
Q403-Categories-in-more-events  
P510_Add_runrecords  

 

Function structure

Form Control Subform Query Table Attribute
F560-Assigning-start-numbers          
  listbox
CurrentCompetition
  Q100-Current-competiton T100-Current-competition  
  button
ButtonShowCU
open
R502-Entries-without-event
     
  button
ButtonShowCat
open
Q403-Categories-in-more-events
Q403-Categories-in-more-events T040-Category
T400-Event
T450-Category-in-event
Q402-Categories-with-more-events
 
 
groupbox
StartNumberReset
       
  button
ButtonAssignStart
Numbers
    T050-Start-number  
      Q562-Start-order T400-Event
T450-Category-in-Event
T500-Competing-unit
 
      Q564-Competing-units T500-Competing-unit  
    call
P510_Add_runrecords *)
     
  Event Action Query Table Attribute
  Form_activate
check that Q560-CU-without-event is empty Q560-CU-without-event Q561-Categories-regular-events
T500-Competing-unit
CUStatus
      Q561-Categories-regular-events T110-Program-block
T400-Event
T450-Category-in-event
 
    check that Q402-Categories-with-more-events is empty Q402-Categories-with-more-events T040-Category
T110-Progam-block
T400-Event
T450-Category-in-event
CatStatus

*) P510-Add-runrecords checks per series for a competing unit if T510-runrecords are present. If not, run records are added.

Module Function Subform Query Table Attribute
P510-Add-runrecords P510_Add_runrecords     T510-Run competing-unit-id

 


Change history

date version change
14-11-02 1.5 Ariadne 4.1, text converted to html