TreeView - Legitimate non-unique keys

[markp99]

I have an application that uses a treeview to load a product hierarchy (n-number of levels deep) for an electroinic system based on a querydef that provides the following data:

Parent | Child | ChildName

I am able to load the treeview control using recursive lookups without an issue. Difficulty arises when a Child assy points to more than one Parent (happens in about 20% of the Systems sampled so far). This is a legitimate condition. Example: CircuitCardA (Child) is used in more than one Box (Parent) in an electronic system (Recordset).

I have played with a couple strategies of concatenating the ParentName with the ChildName, but this breaks the referential integrity of the tree.

Can anyone suggest strategies to deal with legitimate non-unique keys in a Treeview?

 

[FoFa]

Sounds like you are using the wrong key. Have you tried to concatinate the parent/component part numbers to gen. the key? This would work as long as you do not have the same part under the same parent listed more than once.