• Subject: Re: DDS screen: how to ensure field keyed is numeric for alpha-descri bed field
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Tue, 11 Jul 2000 13:55:22 -0500

The problem is that many of the DDS functions, like CHECK, 
will not work with UPDDTA.  IBM explained this to me years 
ago that the 400 adopted the Least Common Denominator between 
the S/38 and the S/36.  Alas, the S/38 didn't have some of the 
functions that the S/36 did with IDDU.

One radical idea is to create yet another file.  Store all possible 
values in this file, like '000001' through '999999'.  Then do a 
ADDPFCST from your customer master file to this file.  This will be 
supported by:  traditional, UPDDTA, C/S, web...





StoneJ@GourmetAward.com on 07/11/2000 12:59:12 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
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


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>DDS screen: how to ensure field keyed is numeric for alpha-described 
field</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">Our database cust# is an alpha field, but we only 
want to allow numeric entries into the field.</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">What is a good way to ensure data keyed into a 
field is numeric using DDS screens?</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">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#.</FONT></P>

<P><FONT SIZE=2 FACE="Arial">Also, I dont want to allow an entry such as 
&quot;0&nbsp;&nbsp; 0&nbsp;&nbsp; 0&quot; (problem, spaces in between).</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">What is the simplest way to accomplish this?</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">TIA</FONT>
</P>

</BODY>
</HTML>

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.