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 6501 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have one table with an unstored calculation field (past due amount). I am trying to write a script to go to another table and set field (expense) with past due amount. The expense field is in a portal on the main layout and I cannot get the past due amount to transfer. All other fields transfer without a problem. Please help.

Posted

Is it just an update problem?

Does the data get entered, just does not show up in portal?

If this is the problem, then you can just add [commit record request] in your script.

If not, then your script needs to be looked at.

What is your calculation?

Attach a clone of your database, I may be able to help.

Posted

what happens is I try to set the field in the expenses table with the calculated field "total expenses" in another table and it will not copy the data in the expenses table. The data just does not show up in the portal. I have several other fields that transfer without a problem into the portal, but the total expenses won't. I tried committing the record and that didn't work either. Thanks for your help...

Posted

If the data shows up in the record, but not in the portal, then it could be a relationship problem. Either you are using the wrong one, it is set up incorrectly, or you need another table occurance.

Calculations involving data from Relationships can be tricky.

Hard to say without seeing your db. Attached your file, or make a demo file.

Posted

Hello,

I see why you are having a hard time with this one.

Your relationships are getting crazy! All over the place.

As far as having your script pull data from one place and put it in another... I believe is a bad idea. You never want the same data in two places. You want to use relationships to relate data from one place to another.

If you insist on having data in two different places, I would suggest using a "look-up". Which still uses a relation. Look-ups are used to store data historically. For example: if you look up data, it enters data as it is at that time, if you change the source of the data, the looked up data will NOT change with it.

I have attached a demo file that may work the concept you are trying to achieve. It is kinda hard to read your file, so we can just develop this demo file to work for you.

BillingDemo.fp7.zip

This topic is 6501 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.