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



Easiest way I can think of is to NOT make the primary file update capable.
Rather, open a logical file (or a second copy of the primary file, using
an OVRDBF for the same file, with a different name), then make that logical
or second copy update capable, and chain to it, then update that file.

I hope you understand that I don't mean copy the file, just open the
original file (IP on the F-spec) a second time (IF U K on the
F-Spec).
Use the Prefix keyword on that logical or second copy.

Assuming your Prefix is "UPD", after the L1 is reached in the program, do
the following

chain updKey updFile ;
UPDField = (whatever you calculated the Field from the Primary file to be)
;
update UPDFileRecFmt ;


In a message dated 4/23/2009 11:09:42 P.M. Jerusalem Daylight Time,
bob@xxxxxxxxxxx writes:

We have an old, large program (that we don't want to rewrite) which
processes a primary file and a secondary file using L1 M1 processing.
Both files are currently input only, and externally defined. At L1
total time an answer is calculated that we want to write back into the
primary file. When we change the primary to update capable, the L1
answer gets written into the subsequent record. We have tried both
UPDATE and EXCEPT, and get the same result: data updates the wrong
(subsequent) record. What's the best (or the easiest way) to update the
correct primary file record? Thanks!


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.