×
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 suspect you've nailed it-- that file has to be cleared!
I've always believed that MBROPT(*REPLACE) just does a clear under the
covers-- mainly because if you can't get a lock on the file you get a
message "error clearing file."
In that case, if I'm desperate to replace the data, I'll use SQL and
Remove from all... Yes, it's slower, but SQL can get a record-by-record
lock and delete them one-by-one faster than shooting all of the users
with locks! Then a CPYF(*ADD) will re-populate the data. Only side
effect is users will see a file with disappearing data that magically
re-appears again, hopefully corrected.
Paul E Musselman
As an Amazon Associate we earn from qualifying purchases.
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
