×
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.
On Jun 29, 2011, at 11:35 AM, rpg400-l-request@xxxxxxxxxxxx wrote:
Best practice: if the file is open, and it is opened in a way that it
*can* lock records, *explicitly unlock* the file before exiting the
program, unless there's an overriding reason to hold the lock.
Or alternatively don't lock it in the first place. You can always add the (N) extender to the READE in which case no lock will occur.
It is a question of how often each scenario (match or no match) will occur and how often you need to actually update. Schadd didn't say what updates were being made or why so it is tough to say.
For example - if the read is positioning to the first of a series of invoices, but only the last one in the chain will actually be updated then I would always use the no-lock option and CHAIN (or READPE) to the one I wanted after a series of READE(N). Same thing if it is common to _not_ find a matching record.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
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.
midrange.com
