×
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.
Three points:
1) Data type N should be under fields. I have often looked at a field
in the code, then gone to the outline view and been unable to find it,
eventually realizing it was data type N.
Those are the ones that should be under fields because they are really
1-byte fields, with the added bonus that you can use *ON & *OFF with
them and say "If NamedIndicator" to evaluate to true or false.
2) Now if the name is defined as part of an *IN data structure or an
INDDS data structure it should probably be under indicators.
3) Off topic: I strongly support the idea of being able to put the
cursor on a field and then some keystroke combination finds it in the
outline, so I can see where else it is used.
Sam
On 9/25/2012 12:35 PM, Edmund Reinhardt wrote:
We would like to know if there is a strong preference to move Named
indicators under the Fields heading so that all fields can be found in one
place and only predefined indicator usage being shown under the Indicators
heading.
On the other hand would anyone be upset about not finding the Named
indicators under the Indicators heading any more?
IBM is listening.
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.
midrange.com
