Download it now!
Bug 103862 - UI: Missing read-only option in form designer for table column of type check box
Summary: UI: Missing read-only option in form designer for table column of type check box
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Database-Forms
  Show dependency treegraph
Reported: 2016-11-11 13:00 UTC by Christoph Kobe
Modified: 2018-07-02 02:35 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Kobe 2016-11-11 13:00:55 UTC
The form designer does not allow one to set columns for tables of type Check Box to read-only, while all other types (e.g. Text Box, List Box, Date Field, Time Field, etc.) can be set to read only.

Steps to Reproduce:
1. Create a database table that contains columns of types bool and varchar
2. Use the wizard to create a form with the table view (default)
3. Edit the newly created form
4. Right click the column for the varchar (type: Text Box) > Column... > General Tab. There is an option "read-only" which can be set to yes or no .
5. Right click the column for the bool (type: Check Box) > Column... > General Tab. Here is no option to set the column to read-only (actual behaviour). I believe here should be a read-only option, too (expected behaviour).
Comment 1 Robert Großkopf 2016-11-11 16:13:20 UTC
Could confirm Read-only couldn't be set for Check Box and Option Button. You could get nearly the same behavior when setting Enabled > No. Only the color of the sign in the box will be greyed out.
I will set this bug to "new" and the importance to "minor", because you could also disable the fields with the same effect.

There has never been an option Read-only for this fields. So I will set this bug to Inherited from OOo.

My system: OpenSUSE 42.1, 64bit rpm Linux, LO, also tested with LO and some other versions of LO.
Comment 2 QA Administrators 2018-07-02 02:35:17 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team