I have a question about a transaction issue I've noticed in a couple mmBusinessObject methods. First, I've noticed that not all of the "FillDataSet()" methods are designed to check for an exising transaction in which to participate. Is this by design, or should it always check to see if the 'Transaction' property is set, and use that transaction?

Also, I've noticed the same thing during the "GetEmptyDataSet()" method call. This results in a call the "mmDataAccessSql.GetEmptyDataSet()", which also has no code to check if there's an existing transaction in which to participate. Was this also by design?

The upshot of all this is that it appears that you'll usually get run-time errors if you call "GetDataSet()" or "GetEmptyDataSet()" in children biz objects of an object after it calls "TransactionBegin()". The error message states that all commands executed using a connection that started a transaction must also have a reference to that transaction. The process of sharing the same transaction on various business objects is a bit confusing.