M
Mike Fechner
Guest
Hi Laura, we do actually still need the ProBindingSource. Situation is the following. We have a lookup control that works on a visible (human readable value) and a technical key (e.g. a GUID). When the user selects a value from the lookup table (let's say Item) both the Lookup's Text/Value (human readable) and LookupKeyValue (GUID) property get's assigned within the lookup (actually an extension to the UltraTextEditor). So the ProBindingSource takes care that the Item.ItemGuid field value, that the Lookup Control assigned to it's LookupKeyValue property get's assigned to the OrderLine.ItemGuid field. It's the same as with binding a Field to a Control's Text/Value/Tag property with the only difference, that the property is ABL defined (and enforced by a .NET Interface, to become member of the .NET's view of the ABL Hybrid type).
Continue reading...
Continue reading...