When using the "View Form Results" to debug my form, I noticed that certain fields did not display results... These fields where all read only, so I wondered if there was a connection. Removed the read only and then results for them were available... is this a bug or a feature? If the former, any plans to correct it, if the latter, how can I make fields read only and still check the results in the "View Form Results"?

OK... let me close out this topic. This is neither a bug nor a feature, just an annoying reality that one needs to work around. The value of a read only field cannot be written to the database, by design.

This makes making a field "read only" not very useful, so I will likely ignore it in the future. Instead I will use (the more round about approach) of a Custom HTML Field to display the value of a hidden field, i.e.

document.getElementById("HTMLDisplayField").innerHTML = ($(HiddenField));

where the Custom HTML Field contains something like:

 

Yes - Read only fields can be helpful /useful but usually when combined with SQL binding or SQL default values. If the value is rendered upon page load (for example a DotNetNuke user default or SQL default) then the value will stick, it's only if you need to modify the value after the page load where that value does not stick.

Thanks!

Chad