How do I use one record to describe a table

I have a table which pertains to an assembly and the individual records of
the table pertain to the components of the assembly. I need one record to
contain information pertaining to the assembly only (Job Number,
Description, etc.). I want this information to appear in the header and
footer of a report. How do I accomplish this?

Thanks in advance.

Re: How do I use one record to describe a table

Bob Sanderson wrote:
> I have a table which pertains to an assembly and the individual
> records of the table pertain to the components of the assembly. I
> need one record to contain information pertaining to the assembly
> only (Job Number, Description, etc.). I want this information to
> appear in the header and footer of a report. How do I accomplish this?
>
> Thanks in advance.

Do it right. Two entity types = two separate tables.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Re: How do I use one record to describe a table

On Nov 19, 12:35 pm, Bob Sanderson
wrote:
> I have a table which pertains to an assembly and the individual records of
> the table pertain to the components of the assembly. I need one record to
> contain information pertaining to the assembly only (Job Number,
> Description, etc.). I want this information to appear in the header and
> footer of a report. How do I accomplish this?
>
> Thanks in advance.

You have one table that contains the item definitions, one row to each
part.
You have a second table whic contains three columns, the parent item,
the child item and the quantity of child item per parent item.

This is a standard way of doing BILL OF MATERIAL type work. Google on
that term and find lots of information.

Q

Re: How do I use one record to describe a table

My thoughts exactly...

"Rick Brandt" wrote in message
news:KZj0j.60237$RX.6706@newssvr11.news.prodigy.net...
> Bob Sanderson wrote:
>> I have a table which pertains to an assembly and the individual
>> records of the table pertain to the components of the assembly. I
>> need one record to contain information pertaining to the assembly
>> only (Job Number, Description, etc.). I want this information to
>> appear in the header and footer of a report. How do I accomplish this?
>>
>> Thanks in advance.
>
> Do it right. Two entity types = two separate tables.
>
> --
> Rick Brandt, Microsoft Access MVP
> Email (as appropriate) to...
> RBrandt at Hunter dot com
>

Re: How do I use one record to describe a table

"rquintal@sympatico.ca" wrote in
news:18cb2116-edfb-4936-88db-27ee7f3c63f0@s36g2000prg.google groups.com:

> On Nov 19, 12:35 pm, Bob Sanderson
> wrote:
>> I have a table which pertains to an assembly and the individual
>> records of the table pertain to the components of the assembly. I
>> need one record to contain information pertaining to the assembly
>> only (Job Number, Description, etc.). I want this information to
>> appear in the header and footer of a report. How do I accomplish
>> this?
>>
>> Thanks in advance.
>
> You have one table that contains the item definitions, one row to each
> part.
> You have a second table whic contains three columns, the parent item,
> the child item and the quantity of child item per parent item.
>
> This is a standard way of doing BILL OF MATERIAL type work. Google on
> that term and find lots of information.

Exactly what I'm trying to create

Re: How do I use one record to describe a table

Bob Sanderson wrote:
> "rquintal@sympatico.ca" wrote in
> news:18cb2116-edfb-4936-88db-27ee7f3c63f0@s36g2000prg.google groups.com:
>
> > On Nov 19, 12:35 pm, Bob Sanderson
> > wrote:
> > > I have a table which pertains to an assembly and the individual
> > > records of the table pertain to the components of the assembly. I
> > > need one record to contain information pertaining to the assembly
> > > only (Job Number, Description, etc.). I want this information to
> > > appear in the header and footer of a report. How do I accomplish
> > > this?
> > >
> > > Thanks in advance.
> >
> > You have one table that contains the item definitions, one row to
> > each part.
> > You have a second table whic contains three columns, the parent
> > item, the child item and the quantity of child item per parent item.
> >
> > This is a standard way of doing BILL OF MATERIAL type work. Google
> > on that term and find lots of information.
>
> Exactly what I'm trying to create

You indicated you wanted to do this with a single table. You need two tables.
One for assemblies and one for components.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Re: How do I use one record to describe a table

"Rick Brandt" wrote in
news:Iwk0j.60238$RX.6913@newssvr11.news.prodigy.net:

> You indicated you wanted to do this with a single table. You need two
> tables. One for assemblies and one for components.

How do I link the two together? I still have to have a unique record in the
components table to link to the assemblies table.

Re: How do I use one record to describe a table

Bob Sanderson wrote:
> "Rick Brandt" wrote in
> news:Iwk0j.60238$RX.6913@newssvr11.news.prodigy.net:
>
> > You indicated you wanted to do this with a single table. You need
> > two tables. One for assemblies and one for components.
>
> How do I link the two together? I still have to have a unique record
> in the components table to link to the assemblies table.

The components table needs to include a field for the assembly identifier. It
will be a foriegn key in the components table and you relate it to the primary
key in the assemblies table.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Re: How do I use one record to describe a table

"Rick Brandt" wrote in
news:wCk0j.60242$RX.25652@newssvr11.news.prodigy.net:

> The components table needs to include a field for the assembly
> identifier. It will be a foriegn key in the components table and you
> relate it to the primary key in the assemblies table.

That's pretty much the problem I have now. Where do I put the foreign key?
Does it have to be attached to every record?

Re: How do I use one record to describe a table

Bob Sanderson wrote:
> "Rick Brandt" wrote in
> news:wCk0j.60242$RX.25652@newssvr11.news.prodigy.net:
>
> > The components table needs to include a field for the assembly
> > identifier. It will be a foriegn key in the components table and
> > you relate it to the primary key in the assemblies table.
>
> That's pretty much the problem I have now. Where do I put the foreign
> key? Does it have to be attached to every record?

Yep, but if you use a form with a subform Access will do that for you
automatically.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Re: How do I use one record to describe a table

"Rick Brandt" wrote in news:yQk0j.60246$RX.23714
@newssvr11.news.prodigy.net:

> Bob Sanderson wrote:
That's pretty much the problem I have now. Where do I put the foreign
>> key? Does it have to be attached to every record?
>
> Yep, but if you use a form with a subform Access will do that for you
> automatically.

Thanks, I'll give that a try

Re: How do I use one record to describe a table

"Rick Brandt" wrote in news:yQk0j.60246$RX.23714
@newssvr11.news.prodigy.net:

> Bob Sanderson wrote:
That's pretty much the problem I have now. Where do I put the foreign
>> key? Does it have to be attached to every record?
>
> Yep, but if you use a form with a subform Access will do that for you
> automatically.

Thanks, I'll give that a try