J
Jack
I have a contact based upon custom contact form with a form level command
button that saves and closes the form (along with doing some other
checking). In certain situations the contact is opened, left open for a few
minutes (5-10) and then the save and close command button is click. What
happens next is some of the time it fails on the close(olsave) with the
message "the operation cannot be performed because the message has been
changed."
I assume this is do to a consistency issue with the open copy and the copy
on the server, however I assumed that in that case it creates a conflict
record and not completely stops the action.
My question is: Is there a way to get around this? If not is there a
generally accepted way to handle this error so it does not throw the error
to the UI?
Jack
button that saves and closes the form (along with doing some other
checking). In certain situations the contact is opened, left open for a few
minutes (5-10) and then the save and close command button is click. What
happens next is some of the time it fails on the close(olsave) with the
message "the operation cannot be performed because the message has been
changed."
I assume this is do to a consistency issue with the open copy and the copy
on the server, however I assumed that in that case it creates a conflict
record and not completely stops the action.
My question is: Is there a way to get around this? If not is there a
generally accepted way to handle this error so it does not throw the error
to the UI?
Jack