× 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've just been caught out by something that should have been obvious but
we missed.  I wondered what the best way to deal with it was

With READ and an indicator, if the record happened to be locked the user
got an error message that was ugly but allowed a retry.  It happened so
infrequently and recovery was so painless that we just accepted it.

We've recently switched to using READ(E) and %EoF etc, using code
similar to:

Read(E) File
Dow             Not %EoF
... Some stuff here
Update  File
Read(E) File
EndDo

but now we don't get the error message if there's a lock, and we fall
through the DoW loop ending up with an update without prior read or
chain.

We could code DoW not %EoF and not %Error, but that's hiding the
problem.  I'd like to be able to give the user the option to retry.

What does everyone else do?  INFDS, register an error handler?

Cheers
Rob



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.