You hit the nail on the head.  I am doing this
for performance reasons.  There are currently less
than 20 hold codes (much less actually, currently
using 4 so I defined the array(s) as 20.  Without
doing something along the lines that I described then
I would have to go out and read the table file for
each hold transaction rather than loading the array
one time and doing a lookup for each hold transaction
(to get corresponding code).  I should always get a
hit on the table (after loading).

Please let me know if you think that I am missing

--- Joe Pluta <> wrote:
> Richard, one quick question: are you doing this for
> performance reasons?
> That is, are you caching data in order to avoid
> doing reads on the file?
> If not, I'd be interested to know why you are doing
> this, since it can cause
> maintenance headaches down the road - you must
> change the program if the
> number of entries ever exceeds the size of your
> array.
> If you *are* doing this for performance, will there
> be a significant number
> of times when you get a "miss" rather than a "hit"?
> If the answer is yes,
> you might want to "backload" the arrays; this can
> substantially reduce your
> processing time.  Let me know and I'll go into this
> a little further.
> Joe
> > -----Original Message-----
> > From: Richard Reeve
> >
> > Thanks to all who responded.  This list is
> certainly a
> > life saver.
> >
> > Happy Holidays to all.
> >
> > Rich
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email:
> To subscribe, unsubscribe, or change list options,
> visit:
> or email:
> Before posting, please take a moment to review the
> archives
> at


Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.