Prev: update a table based on a sum query
Next: Bill of materials - stevie is pimping again.
From: KenSheridan via AccessMonster.com on 23 May 2010 12:22
Take a look at the demo at:

http://community.netscape.com/n/pfx/forum.aspx?tsn=1&nav=messages&webtag=ws-msdevapps&tid=23133


It's the file attached to the second post in the thread and you'll need to
convert it up to Access 2007 if that's what you are using. It is a true BoM
solution in that it handles assemblies and sub-assemblies of an arbitrary
number of levels. It's not intended to be a fully working template, however,
only a demonstration of how the recursive querying necessary to produce a
bill of materials can be simulated in Access.

I suspect that it might not be what you are looking for, however, as what
you've described sounds a lot simpler than a true BoM, and could be much more
simply achieved with tables Parts, Worksheets and WorksheetDetails, the last
modelling a many-to-many relationship between the first two. Post back for
further assistance if necessary when you've taken a look at the demo.

Ken Sheridan
Stafford, England

Egan wrote:
>Thanks for the warnings guys. My requirements really are that simple. If
>no-one can suggest a template, how about some pointers? Access or Excell? I'm
>reasonably comfortable with basic formulas in Excell and I did some messing
>about with Access a few years ago. I'm familliar with one-to-many
>relationships and normalisation etc. I just don't have the time do devote to
>learning it all again from scratch.
>
>> That may not be too difficult a database application to create if your
>> requirements are as simple as they can be... but if you need to define and
>[quoted text clipped - 20 lines]
>>
>> .

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/201005/1

From: david on 23 May 2010 22:19
These are "exploding BOM samples"

http://www.mvps.org/access/modules/mdl0027.htm

http://www.mvps.org/access/queries/qry0023.htm

But it's not completely clear what you require: From your
description, you just want to be able to look up a single
part in a part number table, and add % to the cost? That's
not a template: it's a query using the filter button on the Access
menu.

(david)


"Egan" <Egan(a)discussions.microsoft.com> wrote in message
news:EDD705DF-32D0-4E0B-B9F7-644F7198D873(a)microsoft.com...
> Hi. I need an Access (or maybe Excel) template to help me create bills of
> materials. A worksheet with a list of items (record) with the fields "Part
> number", "description" and "cost". I then need to be able create a BOM by
> entering the "part number" and have the "description" and "cost" as well
> as
> "selling price" (cost + profit %) calculated.
>
> Thanks in advance. Chris.


From: Egan on 24 May 2010 00:20
Thank you for the link Ken.

You're right, what I need is very simple with no requirement for the
sub-assemblies as in your example.



"KenSheridan via AccessMonster.com" wrote:

> Take a look at the demo at:
>
> http://community.netscape.com/n/pfx/forum.aspx?tsn=1&nav=messages&webtag=ws-msdevapps&tid=23133
>
>
> It's the file attached to the second post in the thread and you'll need to
> convert it up to Access 2007 if that's what you are using. It is a true BoM
> solution in that it handles assemblies and sub-assemblies of an arbitrary
> number of levels. It's not intended to be a fully working template, however,
> only a demonstration of how the recursive querying necessary to produce a
> bill of materials can be simulated in Access.
>
> I suspect that it might not be what you are looking for, however, as what
> you've described sounds a lot simpler than a true BoM, and could be much more
> simply achieved with tables Parts, Worksheets and WorksheetDetails, the last
> modelling a many-to-many relationship between the first two. Post back for
> further assistance if necessary when you've taken a look at the demo.
>
> Ken Sheridan
> Stafford, England
>
> Egan wrote:
> >Thanks for the warnings guys. My requirements really are that simple. If
> >no-one can suggest a template, how about some pointers? Access or Excell? I'm
> >reasonably comfortable with basic formulas in Excell and I did some messing
> >about with Access a few years ago. I'm familliar with one-to-many
> >relationships and normalisation etc. I just don't have the time do devote to
> >learning it all again from scratch.
> >
> >> That may not be too difficult a database application to create if your
> >> requirements are as simple as they can be... but if you need to define and
> >[quoted text clipped - 20 lines]
> >>
> >> .
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/201005/1
>
> .
>
From: Egan on 25 May 2010 03:55
I've now made my three tables;
Part, with fields; / Part Number / Description / Cost
Kit, with field / Kit/
and to link them;
PartKit with fields /Kit / Part Number/
and i've got the one-many relationships between the tables.

I can make the form to input the new parts, but I'm stuck with how to make a
form to create a new kit

"KenSheridan via AccessMonster.com" wrote:

> Take a look at the demo at:
>
> http://community.netscape.com/n/pfx/forum.aspx?tsn=1&nav=messages&webtag=ws-msdevapps&tid=23133
>
>
> It's the file attached to the second post in the thread and you'll need to
> convert it up to Access 2007 if that's what you are using. It is a true BoM
> solution in that it handles assemblies and sub-assemblies of an arbitrary
> number of levels. It's not intended to be a fully working template, however,
> only a demonstration of how the recursive querying necessary to produce a
> bill of materials can be simulated in Access.
>
> I suspect that it might not be what you are looking for, however, as what
> you've described sounds a lot simpler than a true BoM, and could be much more
> simply achieved with tables Parts, Worksheets and WorksheetDetails, the last
> modelling a many-to-many relationship between the first two. Post back for
> further assistance if necessary when you've taken a look at the demo.
>
> Ken Sheridan
> Stafford, England
>
> Egan wrote:
> >Thanks for the warnings guys. My requirements really are that simple. If
> >no-one can suggest a template, how about some pointers? Access or Excell? I'm
> >reasonably comfortable with basic formulas in Excell and I did some messing
> >about with Access a few years ago. I'm familliar with one-to-many
> >relationships and normalisation etc. I just don't have the time do devote to
> >learning it all again from scratch.
> >
> >> That may not be too difficult a database application to create if your
> >> requirements are as simple as they can be... but if you need to define and
> >[quoted text clipped - 20 lines]
> >>
> >> .
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/201005/1
>
> .
>
From: KenSheridan via AccessMonster.com on 25 May 2010 13:54
What you need is a form in single form view based on the Kit table, and
within it a subform in continuous forms view based on a query which joins the
PartKit and Kit tables. The subform should include a form footer section.
The subform is linked to the parent form on the Kit fields.

One amendment you'll need to make to your model is to add a Quantity field to
the PartKit table, assuming a Kit might have more than one of each part.
This can then be used to compute the cost.

The query on which the subform is based would be:

SELECT PartKit.[Part Number], Quantity, Description, Cost
FROM Part INNER JOIN PartKit
ON Part.[Part Number] = PartKit.[Part Number]
ORDER BY PartKit.[Part Number];

The PartKit subform would have the following controls:

1. A combo box bound set up as follows:

Name: cboPart

ControlSource: [Part Number]

RowSource: SELECT [Part Number], Description, Cost FROM Part ORDER BY
[part Number];

BoundColumn: 1

ColumnCount: 3

ColumnWidths: 2cm;4cm;2cm

ListWidth: 8cm

Access will convert the dimensions to inches if you are not using metric
units. Experiment with the ColumnWidths dimensions to get the best fit. The
ListWidth is the sum of the column widths.

2. A text box to show the description with a ControlSource of: [Description].
Set its Locked property to True (Yes) and its Enabled property to False (No)

3. A text box to show the unit cost with a ControlSource of: [Cost]. Set
its Locked property to True (Yes) and its Enabled property to False (No)

4. A text box with a ControlSource of:
[Quantity]

5. A text box to show the gross cost per part, with a ControlSource of:

=[Quantity] * [Cost]

6. A text box in the footer to show the gross cost of the kit with a
ControlSource of:
=Sum([Quantity] * [Cost])

Ken Sheridan
Stafford, England

Egan wrote:
>I've now made my three tables;
>Part, with fields; / Part Number / Description / Cost
>Kit, with field / Kit/
>and to link them;
>PartKit with fields /Kit / Part Number/
>and i've got the one-many relationships between the tables.
>
>I can make the form to input the new parts, but I'm stuck with how to make a
>form to create a new kit
>
>> Take a look at the demo at:
>>
>[quoted text clipped - 28 lines]
>> >>
>> >> .

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/201005/1

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: update a table based on a sum query
Next: Bill of materials - stevie is pimping again.