| description | title | ms.date | f1_keywords | helpviewer_keywords | ms.assetid | ||
|---|---|---|---|---|---|---|---|
Learn more about: TN047: Relaxing Database Transaction Requirements |
TN047: Relaxing Database Transaction Requirements |
11/04/2016 |
|
|
f93c51cf-a8c0-43d0-aa47-7bcb8333d693 |
This tech note, which discussed the transaction requirements of the MFC ODBC database classes, is now obsolete. Before MFC 4.2, the database classes required that cursors be preserved on recordsets after a CommitTrans or Rollback operation. If the ODBC driver and DBMS did not support this level of cursor preservation, then the database classes did not enable transactions.
Beginning with MFC 4.2, the database classes have relaxed the restriction of requiring cursor preservation. Transactions will be enabled if the driver supports them. However, you must now check the effect of a CommitTrans or Rollback operation on open recordsets. See the member functions CDatabase::GetCursorCommitBehavior and CDatabase::GetCursorRollbackBehavior for more information.