|
Not only that, but standard field names allow you to use the database cross reference files to find where a particular field is stored. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Bob Cozzi \(RPGIV\)" To: <rpg400-l@midrange.com> <cozzi@rpgiv.com> cc: Sent by: Fax to: rpg400-l-admin@mi Subject: RE: Strange behavior w/%editc() drange.com 02/28/2002 10:04 AM Please respond to rpg400-l Joe, > I wonder how you get that same information - for example, > which fields are from database files. The easy way to do that in RPG IV is to use the PREFIX keyword on your File description spec. I like to use Prefix(CM_) so that all fields from, say the customer master file begin with CM_ in the program. For example, CM_CUSTNAME (or CM_CSTNAM for those that still use 6-character field names). I've always disliked the coding style that people used to name fields in their database with a two or three character prefix. Back then, since we only had 6 characters to deal with, I just could justify using two of them (in 95% of the situations) to associate a field with a file. The PREFIX keyword now allows you to use real field names in your database, and if you like, assign a prefix to those field names at compile time. It's pretty cool. Bob Cozzi _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com 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 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.