Prompt before committing record update

Published 28 September 07 02:39 AM
I just ran across this little video from a how-to on MSDN in which Joel Krist shows how to get Access 2007 to prompt before committing a record update using VBA. 
by Zac Woodall
Filed under: ,

Comments

# Techy News Blog » Prompt before committing record update said on September 27, 2007 9:58 PM:

PingBack from http://www.artofbam.com/wordpress/?p=3535

# Henry Habermacher said on September 27, 2007 11:51 PM:

Hi Zac

I would expect the approach in A2007 should be to using an embedded macro. It would in this case just have two lines.

Condition: MsgBox("Save changes?";36) <> 36

Action: CancelEvent

Arguments:

Condition: ...

Action: RunCommand

Arguments: Undo

Henry

# Henry Habermacher said on September 27, 2007 11:53 PM:

Sorry, the first condition of course should sound like:

Condition: MsgBox("Save changes?";36) <> 6

6 instead of 36

Henry

# Zac Woodall said on September 29, 2007 1:06 PM:

Yeah, you can definitely do this with a Macro too.  The benefit there being that it runs even if the database isn't trusted.  Thanks Henry for pointing this out!!

# Anders Andersen, Norway said on September 30, 2007 1:30 PM:

Zac,

Sorry for posting out-of-subject, but I am unable to get a reply anywhere else :/

I have made an application using Access 2007. When running the application using 2007 Runtime on a machine which has Office 2003 installed, a potentially BIG problem occurs.

The 2007 application runs fine. The problem arises when I start an Office 2003 program afterwards. During startup, the program will go through a 2-minute configuration screen, and it also prompts the user for the Office 2003 CD-ROM. This happens every time I have been running the Access 2007 Runtime application, and then starts Office 2003. How can this be avoided?

I've seen a post somewhere else on the internet about a change in a registry key, but I don't want to change the registry unless I absolutely have to.

I feel that Access 2007 is next to useless as a platform for retail products, as long as this issue resides. My application is ready for sale, but I dare not do it yet because of this. Most companies are still running Office 2003 or older.

Looking forward to your meaningful reply!

New Comments to this post are disabled

About Zac Woodall

Zac is a Program Manager at Microsoft on the team designing Access’s next generation platform infrastructure. He advocates easy to use designs, organizes community efforts, and is the author of The Rational Guide to Microsoft® Office Access 2007 Templates. Zac has been working at Microsoft Corporation since 1999. Before that time, he attended the University of Idaho, from which he holds a B.S. in Computer Science.
Page view tracker