|
I recently has a problem in a trigger programme which resulted in an RNX1024 message , which basically does not tell you very much other that the fact the an error occurred. After 3 days I finally realised that it was a signature error with a service programme. With non trigger programmes such an error is pretty visible with messages in the log etc and thus relatively easy to rectify. Is there a technique for improving the diagnostic information provided when a trigger programme falls over ? Compile time option for example Thanks in advance Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.