Parent Child Relationship via one table
Hello I am rather new to Quickbase.
I anticipate developing a table where users enter our customer company information into. I plan on having a field to designate if the customer company is a parent or a child company. This will be a True False field. True indicates a child company and False indicates a parent company. To designate what parent/company the child/company rolls up to I am thinking of a drop down field which pulls the distinct values of this table (where the roll up designation is false(Parents)) Thus I plan on using one table for parent and the child and designate between parent and child by this field.
Reason for not using classic parent child relationship(two tables)
If I use the classic parent child relationship I would have two tables and in most cases the parent information would be exactly the same as the child. Fully 95% of our customers do not rollup into another company. I am thinking in this situation the users would have to create a parent company for every child when they are exactly the same in order for this to work(duplicating the data entry).
Is there a better way to do this? In addition I am trying to avoid pipeline logic.
------------------------------
michael malchiodi
------------------------------
I anticipate developing a table where users enter our customer company information into. I plan on having a field to designate if the customer company is a parent or a child company. This will be a True False field. True indicates a child company and False indicates a parent company. To designate what parent/company the child/company rolls up to I am thinking of a drop down field which pulls the distinct values of this table (where the roll up designation is false(Parents)) Thus I plan on using one table for parent and the child and designate between parent and child by this field.
Reason for not using classic parent child relationship(two tables)
If I use the classic parent child relationship I would have two tables and in most cases the parent information would be exactly the same as the child. Fully 95% of our customers do not rollup into another company. I am thinking in this situation the users would have to create a parent company for every child when they are exactly the same in order for this to work(duplicating the data entry).
Is there a better way to do this? In addition I am trying to avoid pipeline logic.
------------------------------
michael malchiodi
------------------------------
