I have a layout containing a portal with two rows. By the nature of the database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Charlie
--
Nobody in this country got rich on his own. You built a factory--good.
But you moved your goods on roads we all paid for. You hired workers we
all paid to educate. So keep a big hunk of the money from your factory.
But take a hunk and pay it forward. Elizabeth Warren (paraphrased)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2018-07-14 22:07:21 +0000, Charles H. Sampson said:

I have a layout containing a portal with two rows. By the nature of the database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Charlie

Assuming the values are meant to be different, then the two most likely explanations are either that the Field is not within the first row's
borders in Layout mode, or that the Field is not using the same
relationship as the Portal.

Helpful Harry :o)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Helpful Harry <[email protected]> wrote:

On 2018-07-14 22:07:21 +0000, Charles H. Sampson said:

I have a layout containing a portal with two rows. By the nature of the database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Assuming the values are meant to be different, then the two most likely explanations are either that the Field is not within the first row's
borders in Layout mode, or that the Field is not using the same
relationship as the Portal.

Helpful Harry :o)

I'm not quite sure what you mean by "the values are meant to be
different", Harry. Certainly, the values are coming from two different
records in the related table, which can be verified by the fact that
other fields in the portal are showing distinguishing values. The values
from the two related records are the same, but that's true for values
from another field and they display properly.

I'm also confused by "the field is not within the first row's borders in
layout mode". My problem is that I don't know what you mean by "the
first row's borders". In any case, here's what the Inspector tells me:
The top of the portal is at 2.292" and the right side is at 7.514". (The misfiring field is at the right of the portal.) All of the fields in the
portal have a top of 2.292". That right-most field has a right side at
7.5".

As to your third point, the portal is showing records from the related
table. The field is showing values from a field in that related table.

Here's a new bit of info. I've been tinkering around with some of these dimensions, making the portal larger, the field smaller, etc. When I do,
the borders of the field in the first row are clearly visible, with
white space around them. However, in the second row, this area is
completely blank. In other words, not only is the value of the field
missing, the entire field seems to be missing.

Charlie
--
Nobody in this country got rich on his own. You built a factory--good.
But you moved your goods on roads we all paid for. You hired workers we
all paid to educate. So keep a big hunk of the money from your factory.
But take a hunk and pay it forward. Elizabeth Warren (paraphrased)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2018-07-15 23:31:08 +0000, Charles H. Sampson said:

Helpful Harry <[email protected]> wrote:

On 2018-07-14 22:07:21 +0000, Charles H. Sampson said:

I have a layout containing a portal with two rows. By the nature of the
database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Assuming the values are meant to be different, then the two most likely
explanations are either that the Field is not within the first row's
borders in Layout mode, or that the Field is not using the same
relationship as the Portal.

Helpful Harry :o)

I'm not quite sure what you mean by "the values are meant to be
different", Harry. Certainly, the values are coming from two different records in the related table, which can be verified by the fact that
other fields in the portal are showing distinguishing values. The values
from the two related records are the same, but that's true for values
from another field and they display properly.

I don't know what the data is, but it is possible that some related
records may have the same value in the same field (for example, the
Field might store a person's title, so you'll have multiple related
values of "Mr" or "Mrs"). I'm assuming that for your database the
values are actually meant to be different.

I'm also confused by "the field is not within the first row's borders in layout mode". My problem is that I don't know what you mean by "the
first row's borders". In any case, here's what the Inspector tells me:
The top of the portal is at 2.292" and the right side is at 7.514". (The misfiring field is at the right of the portal.) All of the fields in the portal have a top of 2.292". That right-most field has a right side at
7.5".

In Layout Mode the portal rows have borders / edges. The related fields
*must* be fully within the bordered area of the frst row ... if they
are even one pixel too far and overlap the row's edges, then they can
display "strange" data in Browse or Preview Mode.

You can only put fields in the Portal's first row in Layout Mode. When
in Browse or Privew Modes, FileMaker replicates that row for each
existing related record. Any fields elsewhere in the Portal in Layout
Mode will either be ignored or display 'strange' data.

Usually the 'strange' data is a duplication because FileMaker is
retrieve only the first Related Record's data, rather than the Portal
Row's individual related data.

As to your third point, the portal is showing records from the related
table. The field is showing values from a field in that related table.

When you place a Portal on the Layout you have to choose which
relationship it uses (aka the "Related Table" or "Table Occurrence" in
the new terminology). When you then put the Field's into the Portal,
you have to make sure they are coming from the same relationship in the
pop-up menu at the top of the 'choose a field' window.

If you set the Field using a different relationship (even if it's
actually the same data table), then it confuses FileMaker and display
"strange" data.

The easiest way to check is in Layout Mode - look at the bootom of the
Portal and it tells you the relationship name, then double-click the
'strange' Field and check that the pop-up menu at the top of the
'choose a field' window is exactly the same (you may also need to check
in the Define Relationships window that you haven't got two
relationships with the same name - FileMaker won't care, but it does
make it easy for you to pick the wrong one).

Here's a new bit of info. I've been tinkering around with some of these dimensions, making the portal larger, the field smaller, etc. When I do,
the borders of the field in the first row are clearly visible, with
white space around them. However, in the second row, this area is
completely blank. In other words, not only is the value of the field
missing, the entire field seems to be missing.

Sounds like it *might* be a combination of the two issues. First the
field wasn't within the Portal's first row. When you made the row
bigger it was then inside, but is using a different Relationship to the
Portal.

Probably the easiest thing to do is delete that Field from the Layout.
Then duplicate an existing Portal Field that is working properly and double-click the new duplicate to change which related field data it
displays.


Helpful Harry :o)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2018-07-14 22:07:21 +0000, Charles H. Sampson said:

I have a layout containing a portal with two rows. By the nature of the database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Charlie

Another possibility, although less likely, is that the Relationship
itself is mis-defined, which would lead to you not getting the results
you're expecting.

Helpful Harry :o)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2018-07-14 22:07:21 +0000, Charles H. Sampson said:

I have a layout containing a portal with two rows. By the nature of the
database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

If both fields in the portal are from the same relationship, then the
problem isn't the relationship. The field with a value only in the
first row is apparently not fully within the portal, even if it appears
to be. Select the field and use the keyboard arrows to move the field
10 clicks up (so that it is clearly above the portal) and then move the
field 10 or 12 clicks down so that it is definitely within the first
portal row again.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Charles H. Sampson <[email protected]> wrote:

I have a layout containing a portal with two rows. By the nature of the database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Sorry to be late in following up on this, but I went on vacation and
just got back to checking USENET, after catching up with tons of mail
and email.

It turns out that everybody was right (no surprise). The misfiring field
was slightly out of the portal. Once I fixed that, all is well.

I "discovered' this by shrinking the size of the field's font, then
shrinking the size to the field itself. It was then easy to make sure
that the field lay within the portal and everything worked fine. The interesting effect was that when I enlarged to field back to its
original size, it stayed within the portal. Enlarging the font back to
its original size and all now works as I wanted it to.

As always, thanks to all who helped.

Charlie
--
Nobody in this country got rich on his own. You built a factory--good.
But you moved your goods on roads we all paid for. You hired workers we
all paid to educate. So keep a big hunk of the money from your factory.
But take a hunk and pay it forward. Elizabeth Warren (paraphrased)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2018-08-17 19:40:05 +0000, Charles H. Sampson said:

Charles H. Sampson <[email protected]> wrote:

I have a layout containing a portal with two rows. By the nature of the
database, the table for the layout has at most two related records.

For one field of the related table, only one value is shown, the value
in the first row. Other fields display properly, a value in each row.

Any ideas? Anything I should check that I either left out or didn't
think to do?

Sorry to be late in following up on this, but I went on vacation and
just got back to checking USENET, after catching up with tons of mail
and email.

It turns out that everybody was right (no surprise). The misfiring field
was slightly out of the portal. Once I fixed that, all is well.

I "discovered' this by shrinking the size of the field's font, then
shrinking the size to the field itself. It was then easy to make sure
that the field lay within the portal and everything worked fine. The interesting effect was that when I enlarged to field back to its
original size, it stayed within the portal. Enlarging the font back to
its original size and all now works as I wanted it to.

As always, thanks to all who helped.

Most likely when you re-enlarged the Field you didn't make it exactly
the same height as before, so it still fitted withint the first Portal
row.

Even if a field is 1 pixel too big or 1 pixel overlapping the borders
of first Portal row it can cause this kind of issue, so you must make
sure the borders of the fields are all within the borders of the Portal
row.

Unfortunately FileMaker's zoom / magnify feature is a little bit
flakey, so zooming in to 500% (or whatever) to check the positions can
help, but can't fully be trusted.

The best option is to add the Fields using in the window that appears
when first creating the Portal so FileMaker positions them
automatically, but obviously you sometimes do need to later add other
Fields or stretch Fields longer than the default size.

Helpful Harry :o)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)