Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
What is the VBA syntax for Refreshing the form in the After Update event of one of its controls ?
Hi All,,,
Poor me !"in VBA"....lol.
What is the VBA syntax for Refreshing the form in the After Update event of one of its controls ?
Poor me !"in VBA"....lol.
What is the VBA syntax for Refreshing the form in the After Update event of one of its controls ?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
You would not normally need to "refresh" a form after updating a single control, that control would normally display the value you entered.
However, if you are dealing with some form of cascading controls (where one list or combo box depends on the value of another), then you might try something like:
HTH
Dale
However, if you are dealing with some form of cascading controls (where one list or combo box depends on the value of another), then you might try something like:
Private Sub cboOne_AfterUpdate
me.cbo_Two.Requery
'if you have more than one other control that is dependent, or cbo_Three
'is dependent upon cbo_Two then you would also need to requery that control
me.cbo_Three.Requery
End Sub
HTH
Dale
IF ... you attempt to do this in the AU of a Control ... and the Form is Dirty (in edit mode) ... Access will at that moment attempt to Save your record - which is likely NOT desired at that moment.
Instead ... if necessary ... use the Form AfterUpdate event to do this ...
either
Me.Requery
or
Me.Refresh
depending on what you are trying to accomplish.
Instead ... if necessary ... use the Form AfterUpdate event to do this ...
either
Me.Requery
or
Me.Refresh
depending on what you are trying to accomplish.
There are two options:
Me.Refresh ' Refreshes the current existing dataset - but no new records other may have added
Me.Requery ' Refreshes entire recordsource, including any new records that may have been added.
That's it :-)
Me.Refresh ' Refreshes the current existing dataset - but no new records other may have added
Me.Requery ' Refreshes entire recordsource, including any new records that may have been added.
That's it :-)
As Joe indicates, you could use me.Refresh but all that would refresh the recordset and overwrite your changes.
If you want to write that changed value to the table, then you need:
Me.Dirty = False
The Dirty property of the form gets set to True when the value of any control on the current record changes. To actually write that data to the table, you must save the record which can be done in a variety of ways:
1. move off the record
2. Docmd.RunCommand acCmdSave
3. Me.Dirty = false
#1 occurs automatically if you move off the current record or click on a control that is in a parent or subform.
HTH
Dale
If you want to write that changed value to the table, then you need:
Me.Dirty = False
The Dirty property of the form gets set to True when the value of any control on the current record changes. To actually write that data to the table, you must save the record which can be done in a variety of ways:
1. move off the record
2. Docmd.RunCommand acCmdSave
3. Me.Dirty = false
#1 occurs automatically if you move off the current record or click on a control that is in a parent or subform.
HTH
Dale
"but all that would refresh the recordset and overwrite your changes."
Not after the record has been saved ...
Not after the record has been saved ...
Joe,
The OP didn't say the record was saved. the question was (emphasis mine):
"What is the VBA syntax for Refreshing the form in the After Update event of one of its controls ? "
The OP didn't say the record was saved. the question was (emphasis mine):
"What is the VBA syntax for Refreshing the form in the After Update event of one of its controls ? "
Well sure I get that ... but I went beyond the 'control' aspect ... in that such does not make much sense.
Guess we don't know for sure what the OP intends :-)
Guess we don't know for sure what the OP intends :-)
Joe,
Hope you are having a great day, buddy.
That was why I actually brought up the point of needing to save the current record, before doing the refresh. I can understand that if there is potential for a multi-user environment for a recordset to get dirtied by another user, where the user might want to refresh the forms recordset, but not sure why they would want to after updating a single control.
I have seen applications where the developer committed the record after any control is updated, but I'm against such overkill as it provides no method to allow the user to undo changes to the current record.
Guess we will know what the OP had in mind when he/she checks back in.
Dale
Hope you are having a great day, buddy.
That was why I actually brought up the point of needing to save the current record, before doing the refresh. I can understand that if there is potential for a multi-user environment for a recordset to get dirtied by another user, where the user might want to refresh the forms recordset, but not sure why they would want to after updating a single control.
I have seen applications where the developer committed the record after any control is updated, but I'm against such overkill as it provides no method to allow the user to undo changes to the current record.
Guess we will know what the OP had in mind when he/she checks back in.
Dale
Premium Content
You need an Expert Office subscription to comment.Start Free Trial