Please could someone let me know if my workaround described below to the
"Error 3910 - Transaction Context in Use by Another Session" bug is sensible
or overly complicated and there is a better approach.

I have a DTS package that copies data from one database to other databases -
which may / may not be on the same server (I read from a table in the source
DB to dynamically set the destination connection properties in a loop). I
need to use transactions for a couple of tasks (SQL task and Transform data
task) to ensure I can rollback the destination DB successfully if an error
occurs. I have this working fine when the destination database is on a
different server but ran into the BUG: Error 3910, "Transaction Context in
Use by Another Session" when the destination DB is on the same server as the
source DB.

The workaround I have come up with is to have a separate tasks in my package
- one for databases on different servers and one for databases on the same
server and only allow the appropriate one to run by checking whether the
source and destination servers are the same in the tasks' workflow ActiveX
script. This is working but I'm not sure if I've made it all too complicated
and hard to maintain. Anyone got any comments / suggestions / better ideas?

Thanks