Hi Tomas,

Thank you for the sample application you have provided.

From your initial questions my impression was that you are interested in the specific cell changes, i.e. address of changed cell, its old and new value, what was the exact action, etc. So, that was what the proposed sample was focusing on.

In the case that your requirement is to determine whether any change that modifies the worksheet was performed, my suggestion is to handle the spreadsheet’s CommandExecuted event and check the SpreadsheetCommandType of its e.Command argument:

private void spreadSheet_CommandExecuted(object sender, SpreadsheetCommandExecutedEventArgs e)       
{
               SpreadsheetCommandType command = e.Command;
 
               switch(command)
               {
                              case SpreadsheetCommandType.Cut:
                                             SaveWorkbookDirtied.IsEnabled = true;
                                             break;
                              case SpreadsheetCommandType.Paste:
                                             SaveWorkbookDirtied.IsEnabled = true;
                                             break;
                              //…..
              }
}

Problems still occurring with used approach:

• EditModeExiting-Event: We are actually using this event (as described in the idea) however this alone is not sufficient. The EditModeExiting-Event does not trigger if the user uses paste and delete, because this way he never enters the EditMode. So for us the event can only be used for manual user input and not as a general approach to determine the save-button enabling.
• WorkbookDirtied Event: This was the first event we tried to use since the name suggested that this is exactly what we want, however this event also gets triggered for example when the user starts scrolling through the excel-worksheet (If I had to guess it is probably due to some internal lazy loading) and we don´t want to enable the safe-button just because the user is scrolling and no data changed. Since the additional information that come with this event are very generic and say nothing towards the actual change that triggered the event, this event cannot be used to determine the save-button enabling.

 These answers are of course based on our limited knowledge with the events. If we missed a crucial point you are very welcome to point it out to us, we would be happy if there is already an existing and simple solution for our problem in the product.