Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Relationships on second shown record does not work.

Featured Replies

Hi folks, I've attached a solution I am working on which is used for theatre auditions. I have two records at a time on screen as I see two auditionees at a time. The problem I am having is I was helped with the basic solution by the wonderful BruceR on this forum, and have spent the months since he sent me a working version of what I was trying to create, trying to work out how what he did works (I am pretty green!)

I have since added a bunch of fields to the solution, and cannot for the life of me figure out how to make the related fields show up on the second open record. The basic information is imported into the Camper Info layout from another solution, and then the Stagedoor Audition V2 layout (the main layout I use for the auditions) should get populated when I choose a name from the drop down list. This works for the first shown record, but not for the second one.

Also the show codes and show titles are created in the Show List layout, and when I choose a show code from the drop down list in the the Stagedoor Audition V2 layout, the show name should appear. Again this works in the first record shown, but not on the second. I hope this makes sense and any help would be hugely appreciated as go back into auditions on Monday!

Stagedoor_Audition_file_2010_Clone.zip

In my humble opinion should the graphing look like the above instead.

A thing you might need to study is this:

http://www.filemakermagazine.com/videos/graph-rules-four-rules-to-remember.html

Since your grip on these matters seem wobbly, Further more isn't it healthy structure-vice to base the relational keying on real data, what happens if person changes his name? The rule here is:

http://fmforums.com/forum/showpost.php?post/316371/

Then must I wave a slight astonishment why the incremented key for the second half, is used by a selfjoin to add the photo ... what the heck? What is the rationale in that - not that it matters much since the "allow creation of related record" wasn't turned on!

--sd

graph.jpg

  • Author

Thanks Soren for your help. The rational behind the photo thing is that I have absolutely no clue what I am doing! I literally was given a solution that worked at the point I received it, but when I tried to add to it, I was unsure how it worked so got things done by trial and error. I am creating in the dark! I'm hoping by following the links you kindly gave me that I can learn more :

Perhaps you could be better prepaired for the video, by reading this ahead of watching:

http://www.fmp.it/download/files/FM7_key_concepts.pdf

--sd

  • Author

Thanks again Soren. Changing the relationship graph to your recommendation solved my problem. I am currently going through the links you kindly gave me, which are helping a lot. Thanks again.

Create an account or sign in to comment

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.