Pat is right. Thinking about CELLS in a table indicates that you are perhaps misunderstanding what you are trying to do.
CELLS in a spreadsheet can be anything, do anything. But they don't organize as well as fields in a table. Fields CANNOT be just anything. They have to have values consistent with the field descriptor. Cut/Paste would run into that problem really fast unless you were merely copying from field X in row n to field X in row m.
But besides that, I have had a devil of a time using Cut and Paste functions within Access code. Don't know why, other than the obvious...
If you can open the recordset with VBA, you can just transfer the data to a variable, then update another recordset. Cut/Paste (in the formal sense of a .Cut method or .Paste method isn't really necessary if you have recordset control at the base code level.
That might be why coding Cut & Paste turns into such a bear of a problem.