Question : Refresh, acCmdSaveRecord - Current Record Pointer

Hi,
I have an obscure problem on updating a form and I'm confused as to when to use "DoCmd.RunCommand acCmdSaveRecord" , Refresh, Recalc and Requery.

My understanding is as follows:
"Recalc" will recalculate all calculable fields on the form without updating the underlying recordset and leave the current record pointer at its current position - except on continuous forms when the first record in the set becomes the current record.
"Requery" will update the recordset and re-set the current record pointer to the beginning of the recordset.
"Refresh" will update the recordset and leave the current record pointer at its current position.
"DoCmd.RunCommand acCmdSaveRecord" - when should I use this as opposed to the above and what effect does it have on the underlying recordset and current record pointer?

I would be grateful if someone can set me straight on this please.

Answer : Refresh, acCmdSaveRecord - Current Record Pointer

Yes; issuing Me.Dirty = False cause Access to immediately save the data. Best way would be this:

If Me.Dirty Then Me.Dirty = False
Me.Refresh  <<<