Stuart Rowe wrote:
There's probably an error in the called procedure that is surfacing on that
line in the caller. Carefully inspect (or post) the called routine.

At this point, the customer has had the point-of-failure updated to the latest version of the failing program. Either it will work, or it won't, and if it doesn't, we'll at least know what statement it's failing on.

My test of improving the model still failed to duplicate the problem.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.