"ljubo lecic via AccessMonster.com" <fo***@AccessMonster.com> wrote in
message news:08******************************@AccessMonste r.com...
I am developing a complex ACCESS aplication.
My question is:
If I have A few update queries that are called within
after-update event in the form( queries updating another
tables) I am wandering if the update of the current table
and updates done by updates queries are regarded as
ONE transaction in ACCESS(all done or nothing).
For example, If there is power loss in the middle of my updates queries I
wander If all previous updates are
rolledback.
If there aren't transactions in ACCESS by default
can it be enforced programaticaly?
By default these will not be wrapped in a single transaction. You could
update the form successfully and then 1 or more of your update queries could
fail, but the changes made so far would not be rolled back. You could try
this by getting an update query to do something impossible like set the
primary key to null.
Transactions can be implemented with either DAO or ADO coding. You don't
say which you are using.
Regardless of whether you are using transactions or not, the database may
become completely corrupted in the event of power loss. If you need a
database which will survive a power cut, you need to look at something like
SQL Server.