Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Go to Related Record

Go to Related Record

Go to Related Record

I had thought I'd understood this, but it appears it won't do what I want this to do.

Let's say I have two files - Players and Games, there's a join table called PlayerGames.

I have a portal in Players that lists all the games that player has played; and a portal in Games that lists all the players that have played that game.

I want to click a button in the portal - for example, in Players - that will take me to the ONE record in Games for that game -- instead, Go to Related Record only takes me into the join file.

Is there a way to do what I'm trying to do?



RE: Go to Related Record

Use the Goto Related Record scriptstep to navigate.

Within your script, choose Specify - Define Relationship.
Choose an existing one or make a new one.
Point to the field you need.

Put that button/script in your portal/layout.


RE: Go to Related Record

Hi Jean,

Won't that, however, only take me to the join file? I need to get to the OTHER file...


RE: Go to Related Record

You want to go to a relationship further than the joinfile, this is not possible in lower FM 7 without the tunneling technique or data shunting.

I used both those techniques untill FM 6, but it is a mind and headbreaker, not easy to understand and not aesy to implement when you don't have a great understanding of relationshipstechniques.
The most commonly used technique in FM programming for accessing data from a remote table, is the creation of unstored calculation fields in each of the files in between the location where the data are stored and the file where they are needed.
It may be an effective solution in some cases, however it can cause the field definitions of files to become bloated with large numbers of unstored calculations serving the sole purpose of providing conduits for data being passed up (or down) the line to other files.

Data shunts may do the job relatively effectively when the number of fields is small.

But when I follow your posts, you seem to have a lot of fields....

If there is no way to switch to FM 7 or 8, I suggest you take a look at the datamatrix technique to retrieve values from files further away in your relationships.

Or...I misunderstood your question...This is a FM 5.5 application or not ?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close