The "formspider way" to do it

Hi,

what would be the "formspider way" to do this in best way( not much programming, as possible only defining some selects for validation ) :

Table with some data( gaugeclass, gauge_from, gauge_to, valid_from, valid_to, deviation ). Primary Key is gaugeclass and valid_from, gauge_from and gauge_to may not overlap/coincide.

The Value to set is the deviation.

History is needed, means no real delete, delete will set/update valid_to on actual date, actual record are these, where valid_to is null.

Situation 1 = update of deviation :

The new record shall get the same gaugeclass, gauge_from and gauge_to, a new Valid_from( actualdate) and the new deviation. The valid_to of the old record must be set onto the actual( or given ) date minus one day.

Situation 2 = ( new respectively ) splitting a gauge class :

If a gaugeclass shall be splitted into i.e. 2 classes, the program has to check against overlapping inside the new classes and against the existing gaugeclasses. So this action consists of 1 update of the old record, several check actions( selects ) and 1..n inserts if checks are ok.

At the moment its unclear for me whats the best "Formspider-way" to work with the tool :

• how to control/limit user behaviour
• where/how to get the data for building the checkselects
• where to place the checkselects and how to get the results back
• where and how to define the update/insert statements

Thanks a lot and best regards

Dirk