[AccessD] the dreaded n-recursive parts explosion (BOM) query...again

Thanks Marty!
That's the one
bruce 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Wednesday, 20 July 2005 9:49 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] the dreaded n-recursive parts explosion (BOM)
query...again

Do you mean the nested set solution from Joe Celko It is further written
up in his book "SQL for Smarties"
http://www.mvps.org/access/queries/qry0023.htm
or this one
http://www.mvps.org/access/modules/mdl0027.htm

Bruen, Bruce wrote:

>Hi folks,
> 
>I thought I had got over this one years ago and can't find the SQL 
>query template someone (Lembit???) here kindly supplied last time.
> 
>But it has come back to get me again, so....
> 
>Does someone have a "template" query to return all the parts in an 
>n-level parts explosion, preferably in binary-tree pre-order order.
>* all components, subcomponents and parts are held in the same table,
>* it is a one way tree - i.e. parts that are used in multiple 
>assemblies appear multiple times in the table (i.e.i.e. the pkey for 
>the tree table is not the SKU)
> 
> 
>tia
>bruce
>
>  
>

--
Marty Connelly
Victoria, B.C.
Canada



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
 
 
This e-mail and any attachments may contain confidential information that is intended solely for the use of the intended recipient and may be subject to copyright. If you receive this e-mail in error, please notify the sender immediately and delete the e-mail and its attachments from your system.  You must not disclose, copy or use any part of this e-mail if you are not the intended recipient.  Any opinion expressed in this e-mail and any attachments is not an opinion of RailCorp unless stated or apparent from its content. RailCorp is not responsible for any unauthorised alterations to this e-mail or any attachments. RailCorp will not incur any liability resulting directly or indirectly as a result of the recipient accessing any of the attached files that may contain a virus.