James,

My experience with program-described files is that the key length in the F-spec is only used at compile time. At run time whatever you use as key is 'thrown at the database manager', which handles it. So you might use a data structure as key and at run time use the appropriate layout.

In your case, because the second key field has a fixed length, it might be interesting to try to switch the key fields. If you then use a 13-digit second key field in the key list, I suspect that at run time only the appropriate number of digits will be used.

Joep Beckeringh



James H H Lampert wrote:
Suppose you have a file where you don't know the key length at compile
time, but you do know it at run time. And further suppose you know at
compile time that it will consist of two zoned decimal fields, with the
first one either 9, 11, or 13 digits, and the second one always 5 digits.

Anybody know how to handle that?

--
JHHL

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.