Re: DDS screen: how to ensure field keyed is numeric for alpha-descri bed field

In your DDS you could try setting the Validity Check for a RANGE of '0' to
'999999' (fill nines for whatever your field length is). You won't be able to
key in any alpha, but you might have a problem with leaving the field blank on
an exit. Give it a test.

Darlene




|--------+------------------------->
|        |          "Stone, Joel"  |
|        |          <StoneJ@Gourmet|
|        |          Award.com>     |
|        |                         |
|        |          07/11/2000     |
|        |          12:23 PM       |
|        |          Please respond |
|        |          to MIDRANGE-L  |
|        |                         |
|--------+------------------------->
  >--------------------------------------------------------|
  |                                                        |
  |       To:     "'MIDRANGE-L@midrange.com'"              |
  |       <MIDRANGE-L@midrange.com>                        |
  |       cc:     (bcc: Darlene H Bryant/Banpharm)         |
  |       Subject:     DDS screen: how to ensure field     |
  |       keyed is numeric for alpha-descri     bed field  |
  >--------------------------------------------------------|






Our database cust# is an alpha field, but we only want to allow numeric
entries into the field.

What is a good way to ensure data keyed into a field is numeric using DDS
screens?

I can't chain to the cust file in some cases because ranges are allowed, for
example two fields exist on the screen to key a start cust# and an end
cust#.

Also, I dont want to allow an entry such as "0   0   0" (problem, spaces in
between).

What is the simplest way to accomplish this?

TIA

Title: DDS screen: how to ensure field keyed is numeric for alpha-described field

Our database cust# is an alpha field, but we only want to allow numeric entries into the field.

What is a good way to ensure data keyed into a field is numeric using DDS screens?

I can't chain to the cust file in some cases because ranges are allowed, for example two fields exist on the screen to key a start cust# and an end cust#.

Also, I dont want to allow an entry such as "0   0   0" (problem, spaces in between).

What is the simplest way to accomplish this?

TIA