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



We used to use a similar aproach, but when we added relational integrity to make sure there was a master for the account number, some of the programs that worked "well" before now entered in a loop. It is important to check if the error code (%status) is duplicate key, otherwise do not repeat.

Tony Carolla wrote:

I have a account memo file that is uniquely keyed by account# and memo sequence number. When I want to add a record to an account, I do the following:

- SetGT using the account number
- ReadPE using the account number
- If a record was found, add one to the sequnece number
- If a record was not found, use 1 as the sequence number
- Write the memo with the error extender
- If there was a write error, repeat the loop (somebody added a memo during the above steps)

So this works beautifully until today -- The account being added to was the last in the memo file. The SETGT fails, 1 is used, and the write fails repeatedly. I am trying to find an efficient way to determine what memo number to add. Perhaps I have to resort to SETLL/READE to the end, add one to the seq#. Any ideas?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.