RE: Validating a member name

Hi Don -

>Date: Thu, 9 Sep 1999 08:26:20 -0400 
>From: "Fisher, Don" <DRF@HeiligMeyers.com>
>Subject: RE: Validating a member name
>
>I considered using Joel's suggestion of CHECK(VN), but the field does not
>always have to be entered and CHECK(VN) cannot be conditioned based on a
>value in another field on the screen.  At least, not to my knowledge,
>anyway.

You can't tie the validation of the member name to the value of another
field on the screen via DDS, but you can specify CHECK(VN AB) to allow
the member name to be blank.  If not blank, it must be a valid name.

If when the screen is presented, the field is either loaded with blanks
or with a valid name, you do not need to specify DSPATR(MDT).  If it
could be loaded with a non-valid value, then you do need specify
DSPATR(MDT) on the field to force the field to be validated even if
not changed, thus requiring the user to replace the presented value
either with blanks or a valid name.

The program that handles the screen will have to determine if the
member name being blank/non-blank is consistent with the values in
the other fields on the screen.

Ken
Southern Wine & Spirits of Nevada, Inc.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---