Is there any way of catching the error when a transaction is not found and has been called?.
I've tried a number of things but it does not look possible. The path I'm currently looking at is to check whether the transaction exists (Table TSTC) before the CALL is made, then and only then call the transaction. This sort of gets around the issue. In theory I know this should never happen, but as the menu system currently in place calls transactions and in some cases there are entries for apps that have not yet been created yet and hence have no transaction code yet. The method that I've mentioned will allow a polite message to "transaction does not exist" and avoid short-dumping.
I am surprised that I've never had to do this before and even more surprised that it's not intuitive to capture these errors. Unless anyone know differently.
Bluesky
