I need to create a procedure which will allow to build a Parent/Child schema. To simplify the question I will post an example here:
- Say we have a distributor who sells products (i.e Tom). Tom UserID=1
- Tom has 3 people signed under his name: Christina (with UserID=5), Jerry(with userID=12) and George(with UserID=45)
- Christina signed 2 people under her name. Adam(UserID=34) and Mark(UserID=36)
- Mark signed 3 other people and Adam signed 6 other people,…etc.etc…
I hope you see where am I going…
I need to create a table struvture to implement this procedure so at any given time the App can show the whole structure (like a tree)
For example I will show
[ATTACH=CONFIG]n71335[/ATTACH]
I have some ideas how ti design the database for this but I haven’t done something like this before so need some opinions from those who did
I wonder if anybody has implemented this structure and what is the best practice ?
here is an image showing the graphical chart
ART