×
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.
On 2012/4/25 7:10 AM, Dave wrote:
...
How can I do this? If I declare my wDS like the horribly named DS, my field
names will be wDS.wCstTy, etc.
You can't do that. You have to use LIKEDS to get another copy of the
data structure with the same subfields, and LIKEDS always gives you a
qualified structure.
Well, you could hard-code all the subfields of the entire data
structure, but brr, I hope that your coding standards disallow that kind
of duplication. Even if you defined your subfields with LIKE, your code
would break if subfields were added or rearranged.
Doesn't it go against the spirit, if not the letter, of the coding
guidelines to get around the parameter-naming rule by copying the
parameter to another data structure with a shorter name?
If it's a parameter that can be changed by the procedure, you'd have to
copy it back to the real parameter at the end of the procedure; a
somewhat error-prone task.
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
