field question

[Eric Starn]

Ok I have a table [Assets] with a number of fields in it. One particular
field will be a field called [PCA]. This field will be set up as a look up
field from another table [PCA] that will have the complete list of PCA’s to
choose from. Attached to the PCA field in the PCA table are two other fields,
[Grant Name], [Funding Source].
My question is this, is there away to choose a PCA from a list in the Assets
table and have it pull in and automatically populate two fields also in the
Asset table with the matching data from the PCA table for that record.

Thanks

Eric

 

[Jerry Whittle]

Don't do it. If the other two fields are already in the other table, just
join the tables together in a query when you need to see them.

 

[John W. Vinson]

Ok I have a table [Assets] with a number of fields in it. One particular
field will be a field called [PCA]. This field will be set up as a look up
field from another table [PCA] that will have the complete list of PCA’s to
choose from.

Take a look at http://www.mvps.org/access/lookupfields.htm for a critique of
what many of us consider a misfeature. Lookup fields are NEVER necessary - you
can use a Form with combo boxes instead, and should never use a table
datasheet for data interaction in any case.

Attached to the PCA field in the PCA table are two other fields,
[Grant Name], [Funding Source].
My question is this, is there away to choose a PCA from a list in the Assets
table and have it pull in and automatically populate two fields also in the
Asset table with the matching data from the PCA table for that record.

Unless you want to change the value of the grant name and/or funding source so
that they disagree in the PCA table and the Assets table, these fields should
simply NOT EXIST in the Assets table. Just look them up in a query based on
the PCA ID instead.