TWebDBLookUpCombo with no ListSource

WEB TMS WEB Core
1

I think this is a new behaviour as I can't remember encountering this in a previous WebCore version.

I have a TWebDBLookUpCombo where the lookup list is created in code using Control.LookupValues.AddPair(id, value) so there is no LookupSource set.

So in the procedure TDBLookupComboBox.Change this causes an exception on FListLink.DataSet.DisableControls; as it doesn't check whether a lookuplist is set.

I have a series of dropdowns that are just Yes/No options but have differing values needed, so having a list dataset for each one seems quite heavy.

2

Thanks for reporting.
We applied an extra check for this. This will be improved in the next update.

1 Like
3

A quick workaround - drop on a TWebClientDataset and TWebDatasource and link that up to the ListSource. No need to create fields and no need to open the dataset.

4

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.