Diagnosing LiveBindings Expression Errors in Delphi VCL and FireMonkey Applications

Recognizable Condition

When a LiveBindings expression fails at runtime you may see one of the following:

• The bound control shows stale or incorrect data.
• An EBindingExpressionException is raised (often caught by Application.OnException).
• The UI does not update after the source value changes, even though the binding appears active.

Cause and Diagnostic Table

Symptom	Likely Cause	What to Verify
Control never updates, no exception	Binding expression references a non‑published property or field	Check RTTI/published status of the source member
Exception with message “Property not found”	Misspelled or case‑mismatched member name in the expression	Review the exact expression string
Exception with message “Cannot find source object”	Binding scope error (using Self when the object is owned by another component)	Confirm the binding’s SourceScope or ControlScope
Binding active but UI lags behind source changes	Binding.Active set to false or overridden by code	Inspect Active at runtime and search for code that sets it
Exception inside a converter or custom handler	Converter raises an error or returns an invalid variant	Enable breakpoint in converter or log its input/output

Ordered Checks

1. Inspect the expression – In the Object Inspector or source file, locate the Expression property of the TBindingExpression (or TBindingsource). Verify spelling, case, and that any dot‑separated path matches an existing member.
2. Confirm RTTI/published status – Ensure the source property or field is declared in the published section (or has [Published] attribute). If it is in public or strict private, LiveBindings cannot see it unless you add explicit RTTI via {$RTTI EXPLICIT METHODS(...) PROPERTIES(...) }.
3. Check binding activation – At runtime, read binding.Active (or bindingsource.Active). It must be true. If you set it manually, make sure no later code resets it to false.
4. Look for exceptions – Wrap the binding update in a try/except or examine Application.OnException. An EBindingExpressionException will contain the offending expression and the underlying cause (e.g., missing property).
5. Validate Delphi version and packages – Confirm the project uses Delphi XE2 or later (System.RTLVersion >= 23.0) and that the uses clause includes Data.Bind.Components and Data.Bind.Engines. Missing packages cause the binding engine to be inactive.

Fixes Tied to Findings

• Correct spelling/case – Edit the expression to match the exact identifier (Delphi is case‑insensitive for identifiers, but the binding engine compares the string as written). Example: change Self.Myfield to Self.MyField.
• Add RTTI/published – Move the property to published or add [Published]. If you cannot modify the class, add an RTTI directive:

  {$RTTI EXPLICIT METHODS([]) PROPERTIES([MyField])}

  Recompile and redeploy.
• Activate the binding – Set binding.Active := True; after the form is created, or ensure the Active property is true in the designer. Verify no later code sets it to false.
• Handle converter errors – If you use a TValueConverter, surround its Convert method with a try/except and return a safe fallback value (e.g., Unassigned) when conversion fails.
• Update toolchain – If you are on a pre‑XE2 release, upgrade to a supported Delphi version or install the LiveBindings compatibility pack.

Escalation Criteria

If checks 1‑5 succeed but the binding still does not work or continues to raise exceptions, consider these deeper issues:

• Custom binding converters that raise exceptions internally.
• Cyclic bindings causing stack overflow (e.g., A → B, B → A). Disable one direction temporarily to test.
• FireMonkey style lookup failures on macOS where missing frameworks prevent the control from receiving the bound value.
• Problems in the RTL binding engine itself (rare, but can be investigated by enabling tracing).

To isolate the fault, enable detailed tracing:

• Set a breakpoint in TBindingExpression.Evaluate or TBindingsource.DoAssignValue.
• Use TBindingscope.OnAssignedValue to log the value being applied.
• In FireMonkey, verify that the required macOS frameworks (e.g., Foundation, AppKit) are present in the SDK.

Verification Example

Create a minimal VCL form:

1. Drop a TBindingsource and link it to a TClientDataSet with a TStringField named MyField.
2. Add a TEdit and bind its Text property to the MyField field via the bindingsource.
3. In the Object Inspector, set the binding expression to Self.MyField (correct). Run the program – the edit shows the field value and updates when the dataset changes.
4. Stop the program, change the expression to Self.Myfield (lowercase ‘f’). Re‑run – you will see an EBindingExpressionException with a message like “Property Myfield not found”.
5. Correct the typo back to Self.MyField, rebuild, and verify the edit updates correctly again.

This reproduces the symptom and confirms that fixing the expression resolves the issue.

Limitations and Practical Checks

• Adding RTTI increases the executable size; verify that the increase is acceptable for your deployment target.
• Changing a property’s visibility may affect encapsulation; ensure the change does not break other parts of the application.
• After making any change, rebuild the full project and run under the debugger to catch any binding exceptions that appear during startup.
• Check the Windows event log or console output for EBindingExpressionException messages if you suppress the UI exception handler.