Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 4173 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

HI, I'm trying to create a field which looks up the value of a related Summary field, however I'm getting a value which indicates the summary is being evaluated on all the records in that table, not the related ones. 

 

If I set it to lookup a basic numeric field from the same related table, using the same relationship, it works fine. 

 

If I make a calc field to get the summary value it gets the correct value (I can then set my lookup field to lookup from that calc field within the same table but that seems somewhat long winded)

 

Can you lookup a summary field value not based on all the records  or am I having relationship problems again ?

 

 

thanks

Posted

Hi eos, not really, I want the lookup field in Home table, in the ammended attached I created a Lookup of Calc of the sTotal  (via a self join TO)  howerver the Lookup of Summary evalues all the records regardless of the PK value

 

I have 2 tables Times and Invoice joined by InvoiceID.  the Times holds records with hours worked, and a Summary.  When I create a new record in the Invoice table I wanted the Times::Summary value to be be set in the Invoice:TotalHours .. but I wanted to be able edit the amount, hence using a number lookupfield not a calc field. 

 

It seems a Summary on works on a 'local' found set, not a found set via a TO  ???


sorry, amended file attachd

RelatedSummary_eos.zip

This topic is 4173 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.