Jim Dettman
jimdettman at verizon.net
Fri Jun 18 16:00:44 CDT 2010
I have 3 sample DB's on this; two are an SQL solution; one by Joe Cleko, another by EE was is an improved version of that, and a VBA solution by myself based on a MRPII system I wrote in the mid-eighties. I'll send those along in a minute. Last, an article based on the VBA solution was written up on EE, which I have sent. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D. Tejpal Sent: Friday, June 18, 2010 2:02 PM To: Access Developers discussion and problem solving Subject: [AccessD] BOM - Table Structure For Handling Common Parts In Various Assemblies/Sub-Assemblies. 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 ------------ -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com