Note: The ADO.NET Client attaches the provider-specific prefix "OpenAccess" to the names of the public objects, for example, OpenAccessConnection or OpenAccessCommand.
The ADO.NET Client supports local transactions.
The ADO.NET Client uses 100% managed code in supporting local transactions. Local transactions are implemented within the .NET Framework and use the internal transaction manager of the underlying database.
The ADO.NET Client supports savepoints through the Save() and Rollback(String) methods of the OpenAccessTransaction object.
If your application connects to only one database and you have no requirement to connect to another database, you should use local transactions.