Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.filemaker > #2568 > unrolled thread

Problem with Linked Record in Layout

Back to article view | Back to comp.databases.filemaker

Contents

  Problem with Linked Record in Layout csampson@inetworld.net (Charles H. Sampson) - 2016-02-11 10:15 -0800
    Re: Problem with Linked Record in Layout Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-02-12 16:40 +1300
      Re: Problem with Linked Record in Layout csampson@inetworld.net (Charles H. Sampson) - 2016-02-14 11:54 -0800
        Re: Problem with Linked Record in Layout Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-02-15 18:09 +1300

#2568 — Problem with Linked Record in Layout

In an earlier thread, we established that what I've been doing is not
necessarily bad or wrong. Based on that, here's my problem.

I have a database containing four related tables. (There are two other
independent tables used for generating reports.) Two of the tables are
related with a simple one-to-many relationship. I have a layout for the
table on the "one" side of this relationship. It has three ordinary
fields and a field into the related table. There is also a portal into a
third table. The field into the related table displays the related data
as a drop-down list. Auto-complete is on.

This setup has worked well for a few years. Suddenly, I can no longer
enter data into this field when creating a new record.  The first three
fields are no problem. I can't eve put the cursor into the fourth field.

When I look at an existing record, I see that the drop-down list is
showing values from the wrong field of the related table. Still, when I
enter a "proper" value (from the correct field), it works. The value
displayed is the one I entered. However, clicking in that field again
gives me the drop-down list of values from the wrong filed.

I've had some success with duplicating a existing record and then
editing the copy to have the values I want for the new record. I'm
uncomfortable with that.

Any ideas? As always, thanks in advance.

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)

[toc] | [next] | [standalone]

#2569

In article <1mig8xl.1ecfd0m1tae6wbN%csampson@inetworld.net>, Charles H.
Sampson <csampson@inetworld.net> wrote:
> 
> In an earlier thread, we established that what I've been doing is not
> necessarily bad or wrong. Based on that, here's my problem.
> 
> I have a database containing four related tables. (There are two other
> independent tables used for generating reports.) Two of the tables are
> related with a simple one-to-many relationship. I have a layout for the
> table on the "one" side of this relationship. It has three ordinary
> fields and a field into the related table. There is also a portal into a
> third table. The field into the related table displays the related data
> as a drop-down list. Auto-complete is on.
> 
> This setup has worked well for a few years. Suddenly, I can no longer
> enter data into this field when creating a new record.  The first three
> fields are no problem. I can't eve put the cursor into the fourth field.
> 
> When I look at an existing record, I see that the drop-down list is
> showing values from the wrong field of the related table. Still, when I
> enter a "proper" value (from the correct field), it works. The value
> displayed is the one I entered. However, clicking in that field again
> gives me the drop-down list of values from the wrong filed.
> 
> I've had some success with duplicating a existing record and then
> editing the copy to have the values I want for the new record. I'm
> uncomfortable with that.
> 
> Any ideas? As always, thanks in advance.

It sounds like the field's pop-up menu value list definition is wonky.
Perhaps it's using the wrong field in the Relationship link or simply
using a pre-set value list.

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2570

Helpful Harry <HelpfulHarry@BusyWorking.com> wrote:

> In article <1mig8xl.1ecfd0m1tae6wbN%csampson@inetworld.net>, Charles H.
> Sampson <csampson@inetworld.net> wrote:
> > 
> > In an earlier thread, we established that what I've been doing is not
> > necessarily bad or wrong. Based on that, here's my problem.
> > 
> > I have a database containing four related tables. (There are two other
> > independent tables used for generating reports.) Two of the tables are
> > related with a simple one-to-many relationship. I have a layout for the
> > table on the "one" side of this relationship. It has three ordinary
> > fields and a field into the related table. There is also a portal into a
> > third table. The field into the related table displays the related data
> > as a drop-down list. Auto-complete is on.
> > 
> > This setup has worked well for a few years. Suddenly, I can no longer
> > enter data into this field when creating a new record.  The first three
> > fields are no problem. I can't eve put the cursor into the fourth field.
> > 
> > When I look at an existing record, I see that the drop-down list is
> > showing values from the wrong field of the related table. Still, when I
> > enter a "proper" value (from the correct field), it works. The value
> > displayed is the one I entered. However, clicking in that field again
> > gives me the drop-down list of values from the wrong filed.
> > 
> > I've had some success with duplicating a existing record and then
> > editing the copy to have the values I want for the new record. I'm
> > uncomfortable with that.
> > 
> > Any ideas? As always, thanks in advance.
> 
> It sounds like the field's pop-up menu value list definition is wonky.
> Perhaps it's using the wrong field in the Relationship link or simply
> using a pre-set value list.

I seem to have solved the problem. Instead of having the problematic
field take its value from the "link field" in the related table, I've
changed it to taking its value from the "link field" on the near side of
the relationship. Now I'm able to create new records as I had in the
past. I need to run a lot of tests to make sure I haven't broken
anything.

This seems like a reasonable way to do things, maybe even the best way.
My question now is: Why did it work "correctly" so long with my original
layout?

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)

[toc] | [prev] | [next] | [standalone]

#2571

In article <1mily2l.1lrp8sge0yni3N%csampson@inetworld.net>, Charles H.
Sampson <csampson@inetworld.net> wrote:
> Helpful Harry <HelpfulHarry@BusyWorking.com> wrote:
> > In article <1mig8xl.1ecfd0m1tae6wbN%csampson@inetworld.net>, Charles H.
> > Sampson <csampson@inetworld.net> wrote:
> > > 
> > > In an earlier thread, we established that what I've been doing is not
> > > necessarily bad or wrong. Based on that, here's my problem.
> > > 
> > > I have a database containing four related tables. (There are two other
> > > independent tables used for generating reports.) Two of the tables are
> > > related with a simple one-to-many relationship. I have a layout for the
> > > table on the "one" side of this relationship. It has three ordinary
> > > fields and a field into the related table. There is also a portal into a
> > > third table. The field into the related table displays the related data
> > > as a drop-down list. Auto-complete is on.
> > > 
> > > This setup has worked well for a few years. Suddenly, I can no longer
> > > enter data into this field when creating a new record.  The first three
> > > fields are no problem. I can't eve put the cursor into the fourth field.
> > > 
> > > When I look at an existing record, I see that the drop-down list is
> > > showing values from the wrong field of the related table. Still, when I
> > > enter a "proper" value (from the correct field), it works. The value
> > > displayed is the one I entered. However, clicking in that field again
> > > gives me the drop-down list of values from the wrong filed.
> > > 
> > > I've had some success with duplicating a existing record and then
> > > editing the copy to have the values I want for the new record. I'm
> > > uncomfortable with that.
> > > 
> > > Any ideas? As always, thanks in advance.
> > 
> > It sounds like the field's pop-up menu value list definition is wonky.
> > Perhaps it's using the wrong field in the Relationship link or simply
> > using a pre-set value list.
> 
> I seem to have solved the problem. Instead of having the problematic
> field take its value from the "link field" in the related table, I've
> changed it to taking its value from the "link field" on the near side of
> the relationship. Now I'm able to create new records as I had in the
> past. I need to run a lot of tests to make sure I haven't broken
> anything.

A Value List based on a related field will show up blank or "rubbish"
data if the relationship's link field is empty or isn't right.

It's possible one of the fields on the layout wasn't actually the one
you thought it is, so although it looked wrong to you, FileMaker was
only doing what it was told to do.



> This seems like a reasonable way to do things, maybe even the best way.
> My question now is: Why did it work "correctly" so long with my original
> layout?

Maybe you changed something accidentally / without knowing. Maybe the
file became corrupted and repaired at some point. Maybe a FileMaker
update / file format update changed something.

Helpful Harry  :o)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.filemaker

csiph-web