Is Access ACID Compliant?
No.
Queries run through the Access User Interface are run
as individual transactions, so unless you specifically
turn off transactional handling (as you can when running
a macro action), they are (sort of) ACI (see below).
Durability can be considered to depend on you flushing
the result to disk, which Windows otherwise handles as
a background task.
Jet/ADO/DAO actions are only ACID if they are run inside
transactions. Atomic compliance for single SQL statements
(a basic ANSI compatibility requirement) was turned off
for Jet 3.5 & Jet 4.0: You can only make Jet SQL Atomic
by running inside a transaction.
Jet Transactions are broken. When you run out of locks,
you are supposed to get a 'partial commit', which you
cannot then roll back. I've never seen that happen (for
me, the transaction has always failed), but it's in the
documentation.
Since simple SQL actions are not Atomic, and Transactions
are not Atomic, Access/Jet actions are not ACID.
Access actions were supposed to be ACID in Access 2.0, 1994:
the current situation is just the result of the never ending
process of 'improvement' of the Access platform since then.
(david)