Re: Method of object Failed
This is typical about MTS/COM+, my guess is that you executing some commands on a database, like INSERT or stuff. For some reason (probably because the values used aren't accepted by the database) it generates an error. The error is thrown up to the the calling process (if no errorhandling is implemented that is), which throws it up on his turn and so on until someone catches the error. At least, that is the normal way of business. With COM+/MTS, the error will be thrown up until it reaches the stub, this is an object on the remote computer that acts like the object itself (sounds hard, but that's MTS/COM+). This stub must then throw the error to the proxy (that is the refference to the object on the client side, your VB program). For some (unknown?) reason, the stub may occasionally fail to cast the complete error up to the proxy, resulting in an incomplete error.
From my experience as a COM+/MTS programmer, I can say that 9 times out of 10, this has got to do something with the database.
Tom Cannaerts
[email protected]
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning -- Rich Cook