× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: DDS screen: how to ensure field keyed is numeric for alpha-descri bed field
  • From: Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
  • Date: Tue, 11 Jul 2000 11:10:27 -0700

Title: DDS screen: how to ensure field keyed is numeric for alpha-described field
Define the DDS for the screens as numeric, translate to character within the rpg.
 

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.  Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Stone, Joel [mailto:StoneJ@GourmetAward.com]
Sent: Tuesday, July 11, 2000 9:23 AM
To: 'MIDRANGE-L@midrange.com'
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


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.