[AccessD] BOM - Table Structure For Handling Common Parts InVarious Assemblies/Sub-Assemblies.

    Thanks Arthur!  By SQL page, perhaps you meant MySQL Tips page, which has an item Basic Tree View. Are the tables referred those from Northwind sample db ? 

Best wishes,
A.D. Tejpal
------------

  ----- Original Message ----- 
  From: Arthur Fuller 
  To: Access Developers discussion and problem solving 
  Sent: Friday, June 18, 2010 23:42
  Subject: Re: [AccessD] BOM - Table Structure For Handling Common Parts InVarious Assemblies/Sub-Assemblies.


  This problem has been addressed by multiple authors, including my partner
  Peter Brawley and me, but more leading lights (Celko, Date, et. al.) have
  also touched this. For our solution, visit www.artfulsoftware.com and look
  for "trees" on the SQL page.

  Hope this helps,
  Arthur

  On Fri, Jun 18, 2010 at 2:02 PM, A.D. Tejpal <adtp at airtelmail.in> wrote:

  >    Typical fields for a table having hierarchical list of assemblies and
  > parts are observed to include:  ItemID, ParentID, Description, Qty
  >
  >    With this arrangement, the complete hierarchical chain from each topmost
  > item (having no immediate parent) downward can be worked out right upto the
  > lowest part (having no child).
  >
  >    In situations where a part with same ItemID is needed for more than one
  > Item chain (i.e. more than one top parent), the above table structure might
  > not prove adequate.
  >
  >    Any suggestions - while retaining its role as a self contained table ?
  >
  > Best wishes,
  > A.D. Tejpal
  > ------------