× 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: File field names
  • From: jpcarr@xxxxxxxxxxxx
  • Date: Sat, 28 Oct 2000 13:04:34 -0400


>My personal point of view (not my company's one) is that if
>I use RPGVI, full ILE developement I don't really need to
>use prefix at PF level. Since modules should be short,
>simple and concerned in very specific target I could use
>prefix in the RPG specs. Easy and net.
>But habbits and reality (many programmers and few of them
>using ILE properly) did the choice.
>Marco Facchinetti



While the internal RPG Prefix function  great for the RPG Programmer,   End
Users will still have to qualify their names in any end user query tool.
This might be ok.   But my point is that when we are developing standards,
we should also include the needs of end users who are more and more
becoming the direct(as opposed to in-direct) consumers of the data base.

Outfiles of joined query results are much easier to read with the data base
fields themselves denoting their original source by way of table/field
naming conventions.

IMHO

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.