× 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: Danger! Danger! using IGNDECERR and FIXNBR (was Question abou t RPGIVin V3R1)
  • From: jpcarr@xxxxxxxxxxxx
  • Date: Sat, 20 May 2000 22:11:35 -0400



>> db fields names as screen field names

>are no problem when you use RTNDTA in the DDS.
>Read the screen,
>check the fields,
>read the file,
>read the screen *again* (that works with RTNDTA)
>and update the file.



I couldn't agree more.   This is much better than using work fields for the
display file.  It just makes sense to me to Read, Edit, and Update the Data
Base's Real attributes names(aka field names from file).  The more
variables, and movements you do the greater chance for a mistake. How many
times have I seen a work field name on the screen and the programmer
forgot(and./or it got deleted) to move the data base field name to the work
field name.

RTNDTA is the way to go.   Use the Real Data Base Entity's Real Attribute
name(aka field name).

$.02

John Carr






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

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.