Problem with calculated fields in operation mode

roxmer

Hi,

In the operation mode, when a calculated field is presented in a form and the user try to write on it using backspace to delete the contain, the backspace is interpreted as a back in the explorer window. it causes for instance, to go back to the login page.
Is it a way to avoid this problem? If the calculated field can be presented as a label, I guess there will be no problem with users trying to rewrite in it.

Regards

nlarson

if I recall correctly, all calculated fields are read only, so if a user clocks on one they are actually clicking into 'nothing' so the default browser behavior wins out. If they were actually in an editable field, then backspace works as delete.

roxmer

Hi Larsson! Thanks for your answer.
Yes, that's the way it is, but the problem is that users are too "curious" some times and it happens; they try to write in the read only field! I was wandering if it is possible to show the calculated field as label instead. Otherwise, I just hide it...

aware_support

You can show them inside HTML cells like this:

<<MyObject.MyAttribute>>