I have a form/subform set up that uses the main form to choose a group key
for a set of records that then display in the sub-form.

I am using a SQL update statement in the Mainform.fields afterchange routine
to propogate the new data to all records in the table with the group key.

I have used the requery option on the sub-form to reflect the new change
made on the field from the main to the sub form.  Once the focus leaves the
main form either by jumping to a field in the sub-form OR reading the next
set of group keys for display, I am getting the Write Conflict.  If I simply
ignore the update the underlying table has the correct changes.  

Is there a way to programatically choose the ignore option.  I have tried
Me.Dirty = false to make the main form forget that it had a change, but that
doesnt work.  The SQL update has already forced the write to the disk.  Its
the form buffer that is holding the change and it is mistakenly thinking that
another user has changed the data.  In the routine I know that my code has
made the update and I want a way to force it to take that and ignore the
rest?