Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.
Access 2010: Forms Commit Data Changes When Record Is Changed - Yikes!
Hello - New to Access 2010, I am noticing Access 2010 seems to commit data changes in text boxes, on a bound form ONLY when a different record is displayed on the form - NOT when the focus moves to a different text box (After Update) on the form as in Access 2003! - This behavior is problematic.
I understand it is possible to add the VBA command:
DoCmd.RunCommand acCmdSaveRecord
to the On Change event for all text boxes, but this seems very inefficient - particularly if there are lots of text boxes on the form (and many forms!).
So, how is it possible to have data changes in text boxes committed to the underlying table After Update for ANY text box on a form, without having to add a Do Command to each text box On Change event?
Many Thanks - Jacob
I understand it is possible to add the VBA command:
DoCmd.RunCommand acCmdSaveRecord
to the On Change event for all text boxes, but this seems very inefficient - particularly if there are lots of text boxes on the form (and many forms!).
So, how is it possible to have data changes in text boxes committed to the underlying table After Update for ANY text box on a form, without having to add a Do Command to each text box On Change event?
Many Thanks - Jacob
Asked:
4 Solutions
I agree with peter57r this is how the vast majority of systems work, thats why you have a save/apply button on many forms within programs.
Can I ask why it is that you need the changes to be saved after exit of each field?
Can I ask why it is that you need the changes to be saved after exit of each field?
Actually, the way it works is best because you can CANCEL the entire change of the record, or a single text box by hitting esc (once for current field, twice to return the entire record back to original). Also, you will eventually leave the record, and that's when the changes are saved.
Scott C
Scott C
Jacob,
Not to pile on here, but I would ditto what the others have said; this is the norm.
The only wrinkle Access has is with subforms. When you move to a subform, it comitts the main form record. That is a problem for most because if the user wants to cancel the edit, you'd want to do it as a unit (main and subs), but the main has already been saved and you simply can't undo.
But outside of that, it works as expected.
You also should be aware that most controls have:
.Text - Current value before the user moves focus to another control
.Value - Current value comitted to buffer
.Oldvalue - Value of the control when the record was loaded.
Maybe that will help with what your trying to accomplish.
Jim.
Not to pile on here, but I would ditto what the others have said; this is the norm.
The only wrinkle Access has is with subforms. When you move to a subform, it comitts the main form record. That is a problem for most because if the user wants to cancel the edit, you'd want to do it as a unit (main and subs), but the main has already been saved and you simply can't undo.
But outside of that, it works as expected.
You also should be aware that most controls have:
.Text - Current value before the user moves focus to another control
.Value - Current value comitted to buffer
.Oldvalue - Value of the control when the record was loaded.
Maybe that will help with what your trying to accomplish.
Jim.
Oh, it certainly can be done - using class programming and WithEvents.
Here is how:
http://www.vb123.com/index.html?199812_mk_events.htm
Further about DEEP, Dynamic External Event Procedures, by Shamil Salakhetdinov, the first to describe this in full for practical use:
http://www.vb123.com/index.html?199901_ss_event.htm
That said, most working with this - including myself - have left Access and VBA and turned to Visual Studio and WinForms because if you drive the technique to some limits (well beyond the examples here), Access will crash so you end up wasting your time.
/gustav
Here is how:
http://www.vb123.com/index.html?199812_mk_events.htm
Further about DEEP, Dynamic External Event Procedures, by Shamil Salakhetdinov, the first to describe this in full for practical use:
http://www.vb123.com/index.html?199901_ss_event.htm
That said, most working with this - including myself - have left Access and VBA and turned to Visual Studio and WinForms because if you drive the technique to some limits (well beyond the examples here), Access will crash so you end up wasting your time.
/gustav
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Why is it a problem for you? This is how the entire IT database world works, not just Access. And most other databases require a Save or Submit button to be clicked.