Transactions are not supported on external non-Microsoft Jet data sources, with the exception of ODBC data. For example, if your database has linked FoxPro or dBASE tables, any transactions on those objects are ignored. This means that the transaction will not fail or generate a run-time error, but it won’t actually do anything, either.
You may recall from Chapter 1, “An Overview of Microsoft Jet,” that Microsoft Jet 2.x databases are opened by Microsoft Jet 3.5 as external ISAM databases. However, unlike the other non-native external data sources, the engine does support transactions on Microsoft Jet 2.x databases.
You can check the value of the Transactions property on Database and Recordset objects to determine whether the object supports transactions. A value of True indicates that the object does support transactions, and a value of False indicates that the object does not support transactions. In an ODBCDirect workspace, the Transactions property is available on Connection and Database objects, and indicates whether the ODBC driver you are using supports transactions.