Sets or returns a value that indicates whether multiple transactions that involve the same Microsoft Jet-connected ODBC data source are isolated (Microsoft Jet workspaces only).
Syntax
VOIDSetIsolateODBCTrans(BOOL bFlag);
BOOLGetIsolateODBCTrans(VOID);
Parameters
| Type | Argument | Description |
| BOOL | bFlag | TRUEIsolate transactions involving the same ODBC connection.
FALSE(Default) Allow multiple transactions involving the same ODBC connection. |
Remarks
In some situations, you need to have multiple simultaneous transactions pending on the same ODBC connection. To do this, you need to open a separate CdbWorkspace for each transaction. Although each CdbWorkspace can have its own ODBC connection to the database, this slows system performance. Because transaction isolation isn't usually required, ODBC connections from multiple CdbWorkspace objects opened by the same user are shared by default.
Some ODBC servers, such as Microsoft SQL Server, don't allow simultaneous transactions on a single connection. If you need to have more than one transaction at a time pending against such a database, set the IsolateODBCTrans property to True on each CdbWorkspace as soon as you open it. This forces a separate ODBC connection for each CdbWorkspace.