Re: To skip or not to skip a field in SQL*FORMS

From: <dly_at_vms.macc.wisc.edu>
Date: 26 MAY 93 10:49:59
Message-ID: <1993May26.160031.4758_at_macc.wisc.edu>

I won't reiterate the problem, but I would like to share the solution that we settled on. Many thanks to Carl Pdersen, Marc (no last name), and especially Steven Champness.

Briefly, I would like to skip over some fields depending on what the contents are in a previous field.

I liked Steven's idea of naming the SIN (Skip IF NULL) fields. I put skip_ahead in the ON-NEW-FIELD-INSTANCE trigger on the form level I put skip_back in the KEY-PRVFLD trigger on the form level On all enterable fields, the attribute automatic skip is on.

procedure skip_ahead is
BEGIN
 if NAME_IN(FIELD_CHARACTERISTIC(:SYSTEM.CURRENT_FIELD,PREVIOUSFIELD))

    is not null and substr((:SYSTEM.CURRENT_FIELD),1,3) = 'SIN' then     next_field;
 end if;
END; procedure skip_back is
BEGIN
  previous_field;
  if substr(:SYSTEM.CURRENT_FIELD,1,3) = 'SIN' and

     NAME_IN(FIELD_CHARACTERISTIC(:SYSTEM.CURRENT_FIELD,PREVIOUSFIELD))
     is not null then
     previous_field;

  end if;
END; One worry for the skip_ahead procedure is that if your CURRENT_FIELD is the first field in the block, SQL*FORMS will complain. I haven't come up with a good fix for that condition yet.

Thanks for all your help and interest!

• Debbie Yoshihara University of Wisconsin Department of Biostatistics

Received on Wed May 26 1993 - 10:49:59 CEST