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



Hi Alan -

On Thu, 18 Oct 2012 21:23:05 -0500, aec <cfuture@xxxxxxxxxxx> wrote:

By the way, a word of some caution, there is a subtle difference in the
way the SETLL and READE works when you're using only one key, depending
on whether you (1) define a KLIST with only one key in the list and use
that KLIST, or (2) use the single key value as the key, not as a KLIST.

Don't throw things at me, but I don't remember what it was, but it got
me once.

IIRC, I ran into a problem with a file with multiple key fields where
I used *zero on a SETLL and wanted it to apply to just the first key
field, but it applied to all of the key fields and did not position me
to where I want to be. (Probably the second key field was character.)
IIRC, I ended setting the first key field to *zero, then doing SETLL
with the field.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.