I was overthinking this. My background/knowledge is with Universe database (Avante'), and I was looking at this hard-coded value as a component of the "key" to my EntityGLC record that I thought I had to provide via the Table Relation
What I was trying to do:
On the parent side of my table relations is Part, joining to EntityGLC
Part.Company -> EntityGLC.Company
Part.ClassID -> EntityGLC.Key1
"PartClass" -> EntityGLC.RelatedToFile
What worked, thanks to your help, is I only joined the first two things (Company and ClassID), and added criteria to the EntityGLC table for EntityGLC.RelatedtoFile = "PartClass"
Thanks again. This database/environment is a whole new world to me, after being on Universe (and Pick previously) for 30+ years!
Cindy Lawbaugh
MJMC, Inc.
What I was trying to do:
On the parent side of my table relations is Part, joining to EntityGLC
Part.Company -> EntityGLC.Company
Part.ClassID -> EntityGLC.Key1
"PartClass" -> EntityGLC.RelatedToFile
What worked, thanks to your help, is I only joined the first two things (Company and ClassID), and added criteria to the EntityGLC table for EntityGLC.RelatedtoFile = "PartClass"
Thanks again. This database/environment is a whole new world to me, after being on Universe (and Pick previously) for 30+ years!
Cindy Lawbaugh
MJMC, Inc.
--- In vantage@yahoogroups.com, "Len Hartka" <len.hartka@...> wrote:
>
> Good Day Cindy:
>
>
>
> I am not sure what you are after. How is it different
> than linking the tables as usual and then having a filter to limit it to
> a value.
>
>
>
> There is also the 'Criteria" ability on the Phrase-Build
> tab in BAQ design screen - highlight the table and at the bottom select
> the 'criteria' tab. They can be constants or Prompts.
>
>
>
>