From: hntsignif on
I have a report that has a lookup field from a table on it. The report only
shows the ID for the item and not the text for the item.

I need the text.

I know this is most likely a simple fix but I am having a time.
__________________________
List Table: SeasonList
Table for Report: MarcomPackaging
Field: Season

The field (Season) in MarcomPackaging pulls from the SeasonList table and
then is pulled directly into the report from the MarcomPackaging table.
__________________________

Thanks in advance.

Holly
From: Steve on
Base your report on a query that includes both tables. Include in the fields
from both tables you need in your report.

Steve
santus(a)penn.com


"hntsignif" <hntsignif(a)discussions.microsoft.com> wrote in message
news:3A0C4118-A4CF-43F1-B5F0-E9FC049A8DDA(a)microsoft.com...
>I have a report that has a lookup field from a table on it. The report
>only
> shows the ID for the item and not the text for the item.
>
> I need the text.
>
> I know this is most likely a simple fix but I am having a time.
> __________________________
> List Table: SeasonList
> Table for Report: MarcomPackaging
> Field: Season
>
> The field (Season) in MarcomPackaging pulls from the SeasonList table and
> then is pulled directly into the report from the MarcomPackaging table.
> __________________________
>
> Thanks in advance.
>
> Holly


From: Duane Hookom on
IMO, lookup fields in tables are a horrible "feature". Consider removing them
to remove confusion. If you want to display a field value, you should include
the table containing the field in your report's record source. Add SeasonList
to the record source and join the [Season] fields.
--
Duane Hookom
Microsoft Access MVP


"hntsignif" wrote:

> I have a report that has a lookup field from a table on it. The report only
> shows the ID for the item and not the text for the item.
>
> I need the text.
>
> I know this is most likely a simple fix but I am having a time.
> __________________________
> List Table: SeasonList
> Table for Report: MarcomPackaging
> Field: Season
>
> The field (Season) in MarcomPackaging pulls from the SeasonList table and
> then is pulled directly into the report from the MarcomPackaging table.
> __________________________
>
> Thanks in advance.
>
> Holly
From: tonkaplayer on
You say remove then. How would you suggest the design go? Where would you
put the lookup process and then save that data. Would it be in the table
make fileds to store the data and on a form do a lookup process and store tot
he table? I am creating something similiar. I look up make and model but
now my report shows the not the make name but the autonumber associated with
it.

"Duane Hookom" wrote:

> IMO, lookup fields in tables are a horrible "feature". Consider removing them
> to remove confusion. If you want to display a field value, you should include
> the table containing the field in your report's record source. Add SeasonList
> to the record source and join the [Season] fields.
> --
> Duane Hookom
> Microsoft Access MVP
>
>
> "hntsignif" wrote:
>
> > I have a report that has a lookup field from a table on it. The report only
> > shows the ID for the item and not the text for the item.
> >
> > I need the text.
> >
> > I know this is most likely a simple fix but I am having a time.
> > __________________________
> > List Table: SeasonList
> > Table for Report: MarcomPackaging
> > Field: Season
> >
> > The field (Season) in MarcomPackaging pulls from the SeasonList table and
> > then is pulled directly into the report from the MarcomPackaging table.
> > __________________________
> >
> > Thanks in advance.
> >
> > Holly
From: Duane Hookom on
IMO,
First, you should never be editing records in tables. Use forms with combo
boxes for you entry. Read about the evils of lookup fields at
http://www.mvps.org/access/lookupfields.htm.

If you want to display a descriptive title rather than a number, you only
need to include the table with the descriptive title in your record source
query.

--
Duane Hookom
Microsoft Access MVP


"tonkaplayer" wrote:

> You say remove then. How would you suggest the design go? Where would you
> put the lookup process and then save that data. Would it be in the table
> make fileds to store the data and on a form do a lookup process and store tot
> he table? I am creating something similiar. I look up make and model but
> now my report shows the not the make name but the autonumber associated with
> it.
>
> "Duane Hookom" wrote:
>
> > IMO, lookup fields in tables are a horrible "feature". Consider removing them
> > to remove confusion. If you want to display a field value, you should include
> > the table containing the field in your report's record source. Add SeasonList
> > to the record source and join the [Season] fields.
> > --
> > Duane Hookom
> > Microsoft Access MVP
> >
> >
> > "hntsignif" wrote:
> >
> > > I have a report that has a lookup field from a table on it. The report only
> > > shows the ID for the item and not the text for the item.
> > >
> > > I need the text.
> > >
> > > I know this is most likely a simple fix but I am having a time.
> > > __________________________
> > > List Table: SeasonList
> > > Table for Report: MarcomPackaging
> > > Field: Season
> > >
> > > The field (Season) in MarcomPackaging pulls from the SeasonList table and
> > > then is pulled directly into the report from the MarcomPackaging table.
> > > __________________________
> > >
> > > Thanks in advance.
> > >
> > > Holly