|
Tommy's example of logical files or to go further down into it join logical files, are a good point. However most of the people who argue that this is the better path than to use SQL would be reluctant to use the additional access path's because of some dated belief on early versions of OS/400. Like the philosophy of keeping to a minimum the number of logical files. Not that it is near the burden that it was many, many years ago. On the flip side, there are those sql people who always use an external description and do a select * into :extds regardless of which fields they are actually using. And starting with some ancient version of OS a file change is no longer a simple warning but requires a recompile because of the select * into :extds approach. There are still many people who, instead of creating a good set of logical files have some intense joining defined in their queries and just copy a query around and change some stuff. Frankly that is about the only thing that makes Query/400 daunting to users. So many people go the gui route. And the first setup they have to do in the GUI route that then makes it so much more user friendly is define these join logical's or views. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.