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



I think you're just lucky in this case. Without knowing exactly which
fields are involved with PMPCNV:*input and RF$PM:*output I can't say for

sure, but I can only think of one way this could work.

When you "EVAL toDS=saveDS", you are essentially treating each DS as a
big character variable. So, if the layout of each matches up to the
length of toDS, you will end up with everything in its right place since

the first %len(toDS) bytes of saveDS will be copied to the memory
starting at %addr(toDS).

If that doesn't make sense I can give an example. Just let me know.

That's what I figured, but I knew that there were fields smack dab in the
middle of the saveDS that weren't in the toDS at all. So after reading
your explanation I thought I should determine which fields exactly were
different. Turns out the only differences were in two date fields that
were being broken down into component parts in the saveDS. That's why
they matched, they were 4,0/2,0 in the saveDS and 6,0 in the toDS.

Like you said. I just got lucky on that one. lol.

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