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



Good Morning! 

<snip>
On 5/3/05, Reeve <rfritchman@xxxxxxxxx> wrote:
> 
> Unless there's a reason to do otherwise (such as changing the key), I
> always use the file's key field name(s) in any key field specification
> (in both fixed and ad-hoc formats). This eliminates problems like
> this but, more importantly, it documents the acess logic. It's
> another line of code but it's nice having it there; debugging becomes
> a lot easier.
> 
> -reeve

</snip>


I agree totally, but it doesn't always elim the problems. I was using the 
fields from a DS that was built using LIKEREC against the record format of 
the file itself. The problem was that all keys were numeric, and different 
lengths,,, and they were in the wrong order on the key spec. 



-- 
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought

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.