Desmond Beatty 5/4/2011 8:15:51 AM
A user of the system makes no distiction between a "real" fields and a "look up" field. As far as a user is concerned all fields shown to them are real.
The currentr situation unsatisfactory. The user sees a field value in a (lookup) field in a child record and also in a parent record. When the user searches against that value, only the parent record is returned in the search.
Worse, the response explicitly says "no records found" in child tables.
From a DATABASE perspective it might be understandable (the string is not explicitly held in the securities record).
From a USER perspective this is WHOLLY MISLEADING.
It is INCORRECT from a USER perspective as it MISLEADS the user into thinking there are no matching child records that explicitly pull down and present information from the parent record.
(It is correct NOT to list all child records that do NOT carry down the field from parent as a lookup)
In short, searches should INCLUDE LOOKUPs in table relations.