Portal to display all records from another table

[fmphysio]

I'm having trouble with this and it may be because conceptually I've got it wrong. What I want to create is a portal which displays all records from a table, that contain a certain value.

However, when I placed the portal in, all I get is one record at a time.

I think my relationships aren't right, or perhaps I need to create an extra table?

Any help would be much appreciated.

[mr_vodka]

Seems like you only have 1 table in your scenario. Portal display records from related relationships. If that relationship only has one related record then that it all that will display.

Seem to me like you will need a filtered portal ( search these forums for many examples ) if you need to display those matching records. However if its something constant and you dont want to change it, you can use a calculation field to hardcode it and then create your relationship keyed from this calc field to that data field in your child table occurrence which has the values.

[fmphysio]

Thanks for your quick reply. Maybe I'm confusing both myself and you.

Can I add a new field to the table I want to display, and give it a value of either 1 or 0 ( i.e. display or not), and then create a new table, with 1 field that is related to the original table, and then only have one record with the value 1?? Would that get around this problem.

That way the record it's displaying from the newly created table, would be related to all the records with the value of 1 in that new field.

However, I've tried this and can't seem to get it to work. I think i'm missing something very basic here.

[fmphysio]

Hang on, I think I've got it working.

The problem is that I'm trying to display in the table, fields that are from the related table, and then also a table that's related to the related table, a bit like a friend of a friend.

Now the only problems I have left to solve is only displaying a name once, as it can occur up to 3 times as there could be 3 records.

And also, being able to click on a name and go to their registry file.

Thanks for your help!

Edited April 9, 2009 by Guest

[mr_vodka]

Ok you need to discuss your structure here. What are the tables, the relationships, etc. What is the purpose of your DB? I am thinking that you have some structural issues here.

[fmphysio]

Yeah, I think my structure is quite bad. However, I've since found a way that works.

Basically I've created another table with one record and one value, which is related to a field which is calculated in another.

The portal won't display related records from a calculation, but by changing the relationship it seems to work.

The problem is, I don't really understand why. So I've essentially learnt nothing from this experience.

Anyways, thanks for all your help.

[mr_vodka]

Well first, getting the structure correct will save you hours and hours of rewrite later.

Second, on the child side of the relationship, the key field can be a calculation but ONLY if it can be stored. For example, a calculation that references yet another related table will be UNSTORED. You will not be able to use this calculation field as a match field on the CHILD side. However, you CAN use an unstored calc on the parent side.

Perhaps you can discuss your solution, what you are trying to do, and your current tables so that we can help you with your structure. Be specific with names, not abstract.

[comment]

I think this has become a duplicate thread of:

http://fmforums.com/forum/showtopic.php?tid/202705/

[fmphysio]

Yeah, well originally they were two separate questions in regards to a single solution:

a) the calculation

the portal

Hence the posts in either section.

I now have a working solution so this thread may be closed. Thank you all for you help.

[LaRetta]

There is no such thing as closing a thread ... it will stay forever in FM Forums. And this is one of the reasons why we ask that people just post once; an entire thread will not be deleted because that would be disrespectful to everyone including those who responded and those who may have similar needs.

Yeah, well originally they were two separate questions in regards to a single solution

I suggest you post once in the forum which you THINK may be the best type of solution. If there are better ways, you can be assured we would tell you. And the post would quietly be moved to the proper section later (by the scrubbing-bubble moderators) after it had been resolved. So please only post once and let us worry about the cleanup, okay?

You did nothing wrong but it is how FM Forums works the best. Thanks! :wink2:

Edited April 13, 2009 by Guest

[fmphysio]

That's fine, but I disagree with the duplicate post. Two separate issues, two separate posts.

[LaRetta]

Disagree all you wish. But do not double post in the future. ONE problem, one post. Please.

[fmphysio]

Okay thanks for your help :(