In our application we use several forms for data input. Validation errors are shown beneath the corresponding input field (inline validation).
Now we will also introduce a concept for concurrency situations (two users changing the same data set at the same time). In case of a concurrency situation we will probably have some kind of warning message that tells user2 that user1 made changes to the same data entry. User2 will have to decide whether he wants to save his changes (and override changes made by user1) or discard his own changes and keep the changes made by user1.
Now the question: Would it be a good solution to use the existing validation error visualisation for these concurrency messages (consequence: the user wouldn't be able to visually differentiate between a validation error and a concurrency message)? Or should we use a separate message box for these kinds of concurrency errors?
Here is an example of a (inline) validation error message for an inpuut field: https://plus.google.com/photos/100025793446391279908/albums/5800923977393083297?authkey=CLKBofbap_7KzwE
Should concurrency 'errors' better be handled by a seperate message box above the form that presents the possible actions per error? Here's an example for a concurrency error message: https://plus.google.com/photos/100025793446391279908/albums/5800923977393083297?authkey=CLKBofbap_7KzwE