Created attachment 106532 [details]
Demonstration document Form1 has bug Form2 has workaround
1. Create Form1 with at least one form internally that is not bound to datasource.
2. Create listbox with list.
3. Listbox control does not update a field, but it does have a list and should be able to display SelectedValues.
UNEXPECTED RESULT: Cannot open list on unbound form to display list or display any SelectedValue (for reference purposes, as listbox would not update field).
EXPECTED RESULT: Should be able to display a SelectedValue for visual reference purposes.
WORKAROUND: Bind form to datasource. See Form2 in sample, which is identical except the relevant form is bound to Table1. Now, even though the listbox itself still is unbound to any field, can display a SelectedValue. No practical reason why ability to display a SelectedValue should depend on whether form as a whole is bound to datasource (especially since there is no change to the particular listbox).
P.S.: I would have deleted Module1 macro skeleton in its entirety to eliminate the macro warning ... but apparently that is not an option in LO ?
P.P.S.: Form1 and Form2 both internally have two different forms. I have encountered other unexpected functionality with parallel bound and unbound forms preparing this demo, including a form that mixed up which internal form was supposed to be displaying the navigation buttons, but when the forms got mixed up like that, the bug described here spontaneously disappeared.
The requirement to be bound to a data source dates back to before the LO project was created
Could be a RFE
As an example where what you suggest works already, form controls in a normal Writer document, or an XForm.
Adding self to CC if not already on