× 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.


  1.  Home
  2. RPG400-L
  3. November 2010

Re: Editting a numeric entry field in DDS

Robert,
If the user actualy keyed 8_____452 (underscore represent blanks), then the
VALNUM keyword would catch the error.
If the field already had _____452  and the user just keyed in 8 without using
the Field Exit key, then the CHECK(RZ) keyword would force them to use the Field
Exit which would give you a value of 000000008 returned to the program.



Thanks,

 
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical
Solutions Implementer V5R3

  
 






________________________________
From: Robert Rogerson <rogersonra@xxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Mon, November 1, 2010 1:05:23 PM
Subject: Re: Editting a numeric entry field in DDS

Thanks Jeff,

In the end I did use both the VALNUM keyword and CHECK(RZ).

What prompted this issue in the first place was that the user had
erroneously entered 8_____452 (underscore represent blanks).  If CHECK(RZ)
was used alone the field became 800000452 when returned to the program.
This value was valid and so the program continued with no error.  CHECK(RZ)
alone did not solve the problem.

By adding the VALNUM and the CHECK(RZ) this situation was avoided.  I'm not
sure if you were suggesting the use of both but if you were then I'm just
reiterating it.

Thanks,

Robert Rogerson

On Mon, Nov 1, 2010 at 11:26 AM, Jeff Young <cooljeff913@xxxxxxxxx> wrote:

Robert,
While the VALNUM keyword will test if the field is a valid numeric, you
might
want to use the CHECK(RZ) keyword to force the user to press the Field Exit
key
on the field.
This would prevent the condition you are seeing. ( I am assuming the the
data to
the right of the ____ is left over from a prior entry).

Thanks,

Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions
V5R2
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical
Solutions Implementer V5R3









________________________________
From: Robert Rogerson <rogersonra@xxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Fri, October 29, 2010 1:12:48 PM
Subject: Re: Editting a numeric entry field in DDS

Thanks Cameron,

I had just found and tested it.

Sorry Dennis, I had checked the RPG list and come up empty.  At your
suggestion,  I checked all the lists and finally found VALNUM in the
midrange-l list archive.

Thanks,

Robert Rogerson


On Fri, Oct 29, 2010 at 12:38 PM, Cameron Ross <c.ross.work@xxxxxxxxx
wrote:

Try the VALNUM keyword.

On Fri, Oct 29, 2010 at 11:58 AM, Robert Rogerson <rogersonra@xxxxxxxxx
wrote:

Hi All,

I have an entry screen with a numeric entry field (15, 2).  The user
accidentally entered 8_____452 (underscore represent blanks) and when
the
field exit key was pressed the field was converted to 8000004.52.

I have tried changing the keyboard shift values and added CHECK(FE) but
this
did not invalidate the entry.

What I'm trying to accomplish is that only the right most numbers are
valid,
if a number, followed by a blank and then another number is entered, it
is
invalid.
For example:
  8___452 is invalid as a blank separates the numbers.
452____  is valid as no numbers follow the blank.

This is probably pretty basic but I can't think of it right now.  I
hope
someone knows off the top of their head.

Thanks,

Robert Rogerson
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.