AFAIK, this is because multiple transactions-per-connection may be possible in the future. This is also why the Transaction and Connection properties have to be set separately on a Command object.
Jim > -----Original Message----- > From: Sean Greer (SBI-Chico) [mailto:[EMAIL PROTECTED]] > Sent: 23 April 2002 19:16 > To: [EMAIL PROTECTED] > Subject: [DOTNET] OleDbConnection Question > > > Why did they not make the current transaction available through the > OleDbConnection class? It is truly a pain in the a%# to be > forced to pass > the transaction to every object that is going to do a > database operation > when they could of made it available via a public property on > the connection > object (e.g., OleDbConnection.CurrentTransaction). Any > comments on this? > > Seang > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
