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

Recommended Posts

Posted

I have a layout that is showing information from a different database.

The original db is called job tickets.

The new db is called calendar.

I've created a field in the calendar db called id job number and related it to a field in the job ticket db called job number by an "x" relationship so that i can see all of the jobs from the job ticket db in my new calendar db.

Now, i want to have the id job number display the corresponding job number from the related db in a separate layout.

I've created the separate layout in the calendar db and would like to show the id job numbers in it, but it's not working.

This is sounding more and more confusing as I type. Please, any help would be amazing!

Thanks!

Posted (edited)

Place your cartesian relationship (of your JobTickets) on a calendar layout. Create a global field called gJobID in Calendar (same data type as your JobTickets::JobID primary key. Create a NEW table occurrence of JobTickets and call it Selected_JOB and the relationship should be:

Calendar::gJobID = Selected_JOB::JobID

Now attach script to button over each portal row of your cartesian table occurrence (disallow entry to the fields themselves) with:

[color:gray]Set Field [ Calendar::gJobID ; Cartesian::JobID ]

Go To Related Record [ from table SelectedJOB using layout based upon JobTickets ]

You do NOT have to select anything at the bottom of the GTRR script-step (so skip checking 'show only related' and skip 'match current record' or 'match record set.'

Now when a User selects from the 'cartesian' portal showing all JOB IDs, they will jump to that specific Job Ticket record (using a job ticket layout). If you decide want to end up with just the one JobID in your found set, use the 'match current record only.' Using 'match found set' won't do you any good in this instance, as a matter of fact, since you are relating from ONLY a global on the left, you should ALWAYS only use 'match current record.'

If you use 'match found set' then it will take a lot longer (depending upon how many records are within your calendar table but it won't matter - your result is the same; you've just wasted time doing so.

Edited by Guest
Posted

On the calendar week layout is where is want it to list the job numbers (shown on the jobs layout on the left) that are shipping on those days. Is this even possible?

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