× 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.



Tom,

>I thought I was following the discussion of the issue up to this point, but 
>now I'm lost.
>
>Whay have prefixes at all if they're going to be the same???

Because it would allow EVALC to think the subfields names were the same, thereby
enabling a more corresponding operation.  You'd still have the qualified DS
names to keep the fields distinct.  I agree munging to a common prefix is less
than ideal.

My problem stems from the fact my PF's use unique fields names, which I feared
could inihibit EVALC from matching subfield names.  If we had qualified DS all
along, my PF's would not have used unique field names.

If PREFIX() allowed *dropping* leading characters, my problem would be solved
because than I'd just be replacing those leading characters with the qualified
DS name, and the remainder of the field name would match for EVALC purposes.

I don't think I'm the only one using this type of prefix naming conventions for
PF's.

Doug


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.