Hello all,
I'm working on a project that uses COM4ABAP to call a custom COM object written in classic VB. This maybe a generic RFC question so here goes.
When I call a function like 'com_invoke' over in the COM4ABAP RFC destination, how can I catch errors that might occur? I can't find a CATCH exception to latch on to. Is there a way to keep ABAP from creating a dump? I would much rather catch the issue, log it, and close things up gracefully.
For example, if I call 'com_invoke' and give it a bad COM function name, I would like to catch that execption vs. having it dump. Any clue how to do that?
Thank you.
Crew Reynolds
Daydots
R/3 4.6C