Using Transactions with Access 2007

[dweeber62]

I have a project where the user wants edit and add data (which I
intend on displaying in a subform) without the changes being made to
the database until the user clicks on a "SAVE" button. (This best
mimics what the users are accustomed to.)

Although I've never used "transactions", from my reading, this seems
like the way to go. I would like to hear other opinions from more
experienced programmers.

If it is the way to go, I've not found a great deal of resource
material. The books I have do little more than describe the 3 basic
commands. I'd like to see more information.

Any comments or help is greatly appreciated.

 

[Tom van Stiphout]

On Thu, 23 Jul 2009 20:12:20 -0400, (e-mail address removed) wrote:

No, transactions are not the way to go. They should not be held open
while the user is editing.

I typically put a lot of effort into convincing a client that this
approach is not the best way to go, that alternatives are faster and
thus cheaper to implement, etc. If that does not help, I consider
unbound forms, or temp tables.

-Tom.
Microsoft Access MVP

 

[dweeber62]

Tom:
I am under the impression that if I were to use transactions I would
have to utilize unbound form and subform.

The temporary table concept sounds promising. The project manager is
only insisting that the interface require the user to click a "Save"
button to make any data entry part of the database. I felt like this
requirement was a step backward database design, but his reasoning has
merit.

I'm thinking about the temporary table idea. It seems that syncing the
backend table with the front end temp table would be very similar to
using transactions to update the data.