You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
Comments: (4) Collapse
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
Sorry, the first condition of course should sound like:
Condition: MsgBox("Save changes?";36) <> 6
6 instead of 36
Henry
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!!
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!
Comments: (loading) Collapse