columns

[JB]

Hello
I have a table with Clients (clientId as primary key) and another one with
Calls & Activities (activID primary Key). The second table is used in a
subform in the main Client form and all is working well for the users.
Thing is, I prefer to see the data in the Calls & Activities by way of the
table and although I do have a column called clientName in both tables, the
Calls & Activities table only shows the clientId data but the clientname
column is blank.
What am I doing wrong?
Thanks
(Access2003)

 

[John W. Vinson]

Hello
I have a table with Clients (clientId as primary key) and another one with
Calls & Activities (activID primary Key). The second table is used in a
subform in the main Client form and all is working well for the users.
Thing is, I prefer to see the data in the Calls & Activities by way of the
table and although I do have a column called clientName in both tables, the
Calls & Activities table only shows the clientId data but the clientname
column is blank.
What am I doing wrong?

Just using Microsoft's misdesigned, misleading, infuriating so-called Lookup
field type.

http://www.mvps.org/access/lookupfields.htm

Your table APPEARS to contain a client name. It doesn't. It only contains the
ID, and that fact is concealed from view by the Lookup Wizard.

Why not just use a Combo Box on the subform? This can easily be set to store
the ClientID while displaying the name (in fact the combo box toolbox wizard
will do it by default).

 

[JB]

Hello
Sounds good except that would effect the subform and show the name, which i
don't want as the main form shows the name.
I only want it to show on the table.
Ta

 

[JB]

Thank you. That's it. I've see that before.
And I set this new query as an Update query right?

Ta

 

[JB]

Thanks so much for your help. Did what you said and it worked really well
I'm so pleased.

Jenny

 

[John W. Vinson]

Hello
Sounds good except that would effect the subform and show the name, which i
don't want as the main form shows the name.
I only want it to show on the table.

Why?

Users should NEVER need to see table datasheets. Tables aren't designed for
data presentation, but for data storage.

 

[JB]

I didn't want it for the users I wanted it for myself to look at the data
like in a spreadsheet, the query was perfect
Jenny