bluey,
If you have a write conflict, there is something wrong with the way your form is working. You need to fix that rather than trying to find an alternate way to save the current record. Is the form bound to a query or the table? Do you have some other form open at the same time bound to the same recordsource? A form with a subform bound to the same recordsource as the main form would conflict. A form that opens another form that uses the same recordsource as the first form would conflict.
Carolyn,
Your question is out of context so I don't know what you are trying to do. Travis was suggesting that bluey look in help for:
Docmd.RunCommand acCMDSaveRecord
This command is used whenever you want to save the record yourself in code. This is necessary if you have built a save button on a form or if you open a second form or report from the first one and the subsequent form/report needs info from the first form. If you haven't yet saved the current record, the subsequend form/report cannot "see" it.