How to force an update

[bginhb]

I have a form that displays/updates multiple records. One field in the record keeps track of hours but is restricted to hours and quarter hours. As part of the implementation the User is permitted to update the field for hours and an unbound combobox containing quarter hour plus and minus values - i.e. -0.75, -0.50 ... +0.50 is being used to micro adjust the hours field. The form also totals the hours field using a textbox in the form header using a domain aggregate.



Since the hours field is not being updated by User data entry the "dirty" property is not triggered and I am at a loss to figure out how to trigger a field update so the summary hours textbox will update.

Appreciate any assistance ... Thnx.

[RuralGuy]

You can update the control from any other control in code.

[bginhb]

Thanks RuralGuy but I don't see how that solves the problem.

The summary control is a textbox that uses a domain aggregate (Dsum) to add the values of all the hours fields. The combobox is used to add or subtract 1/4 hours from the value of the Hours field and I want the resulting hours amount to be immediately summarized in the summary control. I don't know how to achieve that without finding a way to trigger an update to the hours field so that a requery to the summary control will produce the correct total.

[RuralGuy]

Me.YourTextBox.Refresh(or Recalc) should do it.

[bginhb]

I'm afraid it doesn't.
If I understand correctly a refresh of a bound textbox will merely refresh the box to the value in the underlying table. That's the opposite of what I need to achieve.

I need to have the value of the textbox updated into the underlying table so that a refresh of the summary total box (using Dsum) will be able to sync with the screen that shows an updated value that was created using the combobox.

[RuralGuy]

Have you tried a Me.Recalc which will Recalc the entire form?

[bginhb]

I have but this is a problem at the record level. How to get Access to update a record without leaving the record.

What I do to get this to work after a manual entry to a bound control is to code the AfterUpdate event "If Me.Dirty Then Me.Dirty = False". Setting Me.Dirty to False causes the current record to update to the values in the form controls without having to leave the record. So I learned from Bob Larson the other day.

But when I use a control (combobox in this case) to make additions or subtractions to a bound control the Dirty Event is not triggered and setting it to false as indicated above, does not trigger an update. The combobox solution is quite elegant from an interface point of view so I'm reluctant to let it go and I'm looking for an alternative way to get access to save the data in the controls to the underlying table/query without leaving the current record.

[pbaldy]

Is this what you're after?

DoCmd.RunCommand acCmdSaveRecord

[RuralGuy]

In addition to Paul's suggestion, I also believe Me.Dirty = False will save the current record without regard to the current value of Dirty.

[bginhb]

Thanks folks,
I tried using me.dirty = false and could not get it to work ... that's what began this current thread, but I may have overlooked something so I'll check it again.
If that doesn't work I'll try the DoCmd alternative.
Thank you both!

[boblarson]

The difference between

If Me.Dirty Then Me.Dirty = False

And

DoCmd.RunCommand acCmdSaveRecord

is that the first one will only run if a bound field is changed. The second will attempt a save regardless. So the second may be what you need.

[RuralGuy]

Bob,
I believe my comment in Post #9 is valid as well. It does not test the Dirty property.

[bginhb]

Apparently me.dirty=false does work and I made another error that caused me to believe it didn't.

Sorry for troubling you folks but thanks so much for helping resolve my problem.

[RuralGuy]

Thanks for posting back with your success.

[corrie]

I just have to say that my problem had zero, zilch, nothing to do with this rather old discussion, but between the various comments a major schlepp for this old man was resolved.
I've kinda lost the ability to remember all the syntax, but the logic's still fine. Need some reminders though.
Thanks!