[Migrated content. Thread originally posted on 10 June 2004]

Testing with the 6.0.0 thin client runtime and with the object compile in both 5.2.1 and 6.0.0, when the COM object that I am accessing throws an exception, thin client dies immediately. When running in fat client with the same COM object, it works just fine.

The COM object is a custom .NET dll that has been setup for COM interop. We have the following in our declaratives which is supposed to catch this I thought:

Object-Exception-Handling Section.
use after exception on object.
Object-Exception-Handler.
call "C$EXCEPINFO" using Error-Info, ERR-Source,
Err-Description

And it does catch the exception when running in fat client.

Any ideas what we might be doing wrong? or might this be a bug that is possibly fixed in 6.1 or 6.2?

Dan
Infotrax Systems