Maxmix
Member³
Hi,
Very often, I receive the following (expected) exception, when running some code, making distributed DML calls.

In this example, it was INSTEAD OF trigger, that did some updates on remote databases.
For unknown reason, the error is fatal. I am clicking on the "No" button, and the application enters in "not responding" state, for ever.
Annoying!
Very often, I receive the following (expected) exception, when running some code, making distributed DML calls.

In this example, it was INSTEAD OF trigger, that did some updates on remote databases.
For unknown reason, the error is fatal. I am clicking on the "No" button, and the application enters in "not responding" state, for ever.
Annoying!