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



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 06/12/2018 03:03:58
PM:
Personally, if I understand Dave's solution correctly, I like his
better.
With the solution you're using, you are relying on field Camtday01
starting
in position 97 forever. What happens if you ever change the length of a
field in this record before Camtday01? The program will recompile just
fine, but will likely bomb once you run it because it is expecting your
array to start in position 97 but it doesn't anymore. If you're really
unlucky, it won't bomb, but will give bad results that you might not
recognize until it's too late.

With Dave's solution, again if I understand it correctly, you don't have
to
rely on Camtday01 starting in position 97. Instead, it will use the
address
of Camtday01 as the starting point, no matter where it is actually
located
in the record.


And lest anyone misunderstand exactly what was suggested vs. what
was implemented... Alan combined two different suggestions to come up
with his solution. What Birgitta suggested is not what Alan implemented.
Birgitta's suggestion would work just fine even if the fields shifted in
the record. I use my suggestion (because it is less work to code) in the
case that the fields are actually contiguous in the record. I would use
Birgitta's suggestion when they are not -- although, as I said, her
suggestion would work in either case.


Sincerely,

Dave Clark

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.