We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
10 days, 3 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Access 2010: Forms Commit Data Changes When Record Is Changed - Yikes!
Posted on 2012-03-31
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
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
6 Comments
Active 6 days ago
It's not possible. If you want to save changes on every data change you have to put to Save command into your code.
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.
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.
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
Active today
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.
Active today
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
Featured Post
Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
The Windows Phone Theme Colours is a tight, powerful, and well balanced palette.
This tiny Access application makes it a snap to select and pick a value. And it doubles as an intro to implementing WithEvents, one of Access' hidden gems.
If you need a simple but flexible process for maintaining an audit trail of who created, edited, or deleted data from a table, or multiple tables, and you can do all of your work from within a form, this simple Audit Log will work for you.
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database.
Split up all multi-value fields into single values:
Split up fields that belong to other things into separate tables:
Make sure that all record…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month10 days, 3 hours left to enroll
624 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.