Al Campagna said:
But, in the query behind the report, you'll need to link that same RDIngPKIDDescription
(from whatever table you got it from for your combo) to the RDIngPKID being reported on.
However you linked ID to Desc in the form combo, you'll have to do the same in the
report query.
Thanks, Al. That makes sense however there's a bit of a complication and
I'll do my best to spell things out. I'll refrain from going into all of the
horrific details but please trust that this design is correct and logical
within the context of this particular database.
The Description field is indeed in the report's query:
SELECT tblProfiles.*, tblProfilesRevisions.*, tblProfiles.Description
FROM tblProfiles INNER JOIN tblProfilesRevisions ON tblProfiles.txtProfileID
= tblProfilesRevisions.txtProfileID;
RDIngPKIDDescription uses tblProfiles.Description based off the selected
value in RDIngPKID.
tblProfiles.txtProfileID is the Master Link for the report. So what happens
is that the Description field appears in RDIngPKID according to txtProfileID
and NOT according to the value in RDIngPKID.
WHEW!
I hope that makes sense!
It seems to me that I may need to create an alias Description field in the
query...?
JohnLute said:
I have a form in which field RDIngPKIDDescription gets populated through this
code in its Control Source:
=[RDIngPKID].[Column](1)
I need this in my report as well but haven't a clue how to make it happen.
The field in my report is also RDIngPKIDDescription.
Is it possible to populate the report field?
Thanks!