Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
TN047: Relaxing Database Transaction Requirements
Collapse the table of content
Expand the table of content

TN047: Relaxing Database Transaction Requirements

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.

Community Additions

ADD
Show:
© 2015 Microsoft