Re: displaying an "alias" value in a table

Allen, thank you very much for responding. I certainly understand the
"confusion" part of the argument. I knew that the first time I used it. I did
make note of it in the table design view for each field (3) in which it was
used. It made the table more readable for those for whom I was creating the
application, and it seemed like a good idea.

I am experimenting with a new idea for my current project, and may have a
slightly different use for the "effect".

Thanks again for the assist.
--
Norm Shimmel
Butler, PA


"Allen Browne" wrote:

Open the table in design view.
Select the problem field.
In the lower pane of the table design window, click on the Lookup tab.

You will see that it is set up as a Combo, where the bound column is
zero-width. Change it to Text box if you just want to see the number.
Alternatively, set the width of the first column to (say) 0.4" so that it
shows the number, but you still keep the combo.

Some of us believe that having combos in your table just confuses people
about what is really there. To read more about that opinion, see:
http://www.mvps.org/access/lookupfields.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"NES" <NES@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:07B5D79B-E92A-47C6-8C51-EF7DD02E03E3@xxxxxxxxxxxxxxxx
I created a DB a year ago in which one of the tables holds input from a
form.
Several of those table fields hold record numbers from other tables or
queries, HOWEVER the table field display substitutes the information in
lieu
of the record number.

For instance I might select "Mary Ann" from a dropdown list. Mary Ann
happens to be record number 35 in that lookup table. However, the table
this
information is then stored in hold the number 35. But it displays "Mary
Ann"
in spread*** view.

I don't know where I learned to do that. Looking at either table gives me
no clue. How does one do this?

I need to do it again. Thanks very much.
--
Norm Shimmel
Butler, PA


.

Quantcast