Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

Posted

I have a REPORT table with ReportID; ReportNAME.

I have a SUPPLIER table with ID; Name; etc.

I have a SYSTEM table with globalRequestedReportID.

When on a form: SupplierDetail based on SUPPLIER, I have a print button

to print the current supplier info. Thru a series of

CustomDialogues, I generate a reoprt id that is set in globalRequestedReportID.

Then later in my print button script i use GoToLayout Name by calc...

I use a relationship between

SYSTEM::globalRequestedReportID and REPORT::ReportID to get the ReportName

to use for the printing of the supplier info.

AND NOW THE PROBLEM...

This only seems to work for the 3rd record in my suppliers table...

When i move to another record and give the same answers to the

dialogue questions thus generating the same key for a ReportID match it fails.

Any ideas?? The weird part is that the questions & ReportID require no info

that is based on what record i am on.

Thanks

Dan

Posted

I fixed it!!

What i forgot to take into account is that scripts run based on the

active layout when they are triggered....

so in my print script i needed to go to a layout that was

based on the SYSTEM table before using the go to layout by calculated name step.

FileMaker could not figure out what report to link to because my

starting point was the SUPPLIER table which is not linked to REPORT table.

So goint to a basic layout that is based on SYSTEM table made the link work.

Thought I would share my results for others to use..

Dan

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