|
Then I put a breakpoint on the assignment, run the job, and wait until
it breaks. Looking at the program stack tells me exactly where the
problem came from. I can even add the offending program to the debug and
browse the variables in it for more information. Works pretty well in
situations where the problem could come from a lot of different programs.
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.