Error editing protected spreadsheet

Thanks but how can I trap this error then as I do not want it to be displayed.

To avoid the exception, you can use the TApplicationEvents.OnException event.

But surely if I set editing to false, like other of your components, this should not raise an error!

Yes, this behavior is correct. The Editing option is included in the spectrum of the document protection. So, when you disable the Editing property, you get the same exception as when you enable the Sheet protection.

I think what simple ReadOnly property without any exception is the good idea for create read-only spreadsheet and check exception in TApplication.OnException is not very good and idea, because, as sample, in my application user may have protected sheet and raise exception is correct and may have spreadsheet only for view (not editiing) and raise exception in this is not nice solution.

One of the great things about DevEx components is the uniformity between them however, in this case, it is unfortunately inconsistent. The generation of an error in this case may be design, but in my opinion, incorrect.

Developing our SpreadSheet, we oriented on the Excel behavior. It has no "ReadOnly" mode and always shows a message if you try to edit a protected Sheet.

Please make this optional!

I understand your idea. We will consider it.

Make up to topic:)
Also problem with using Protection as ReadOnly-spreadsheet is when i want prevent enduser edit my spreadsheet i make it's protected := True and when i save my spreadsheet, spreadsheet saved as protected xlsx-file and enduser must in excel do unprotect.
i think simple runtime (not saved to Excel-file) property ReadOnly for SpreadSheet and SpreadSheetTableView decide many problems without any workaround.

Hello Alexander,

I understand your idea and we will discuss it with our developers. Thank you!.

Hi, is there any simple way to disable built-inException occurence in runtime when sheet is protected or use custom dialog?

Hello Michal,

You can handle these exceptions like any other exceptions in your application. Place the TApplicationEvents component onto your form and handle the OnException event.

This is utter nonsense that clicking on the spreadsheet causes this error. Please implement a readonly property as you have for other components.

+100500 ;)

To chip in here, I've also just been surprised by the exception-throwing behaviour of a TdxSpreadSheet I want use for display-only purposes in a form.

A workaround for this seems to be to leave the OptionsBehaviour.Editing property as True, but add a handler for the OnEditing Event and in that have an unconditional AAllow := False to block all individual attempts to start an edit.

That said, I agree that the current behaviour is both inconsistent with other DevExpress controls, unintuitive and inconvenient (whether it's consistent with Excel or not) and would really appreciate a new "just don't allow edits" facility in later releases.

A followup to this; if it isn't practical to add the new "don't allow edits" functionality, can the exception raised on attempting to edit a read-only sheet be changed to a specific type, rather than the generic EdxSpreadSheetError that's raised at the moment?

Hello Ian,

Please check if handling the TdxSpreadSheet.OnEditing event in the following manner is sufficient to accomplish your task:

Delphi
procedure TForm2.dxSpreadSheet1Editing(Sender: TdxSpreadSheetCustomView;  
  var AProperties: TcxCustomEditProperties; var AAllow: Boolean);  
begin  
  AAllow := False;  
end;