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

Groups > comp.databases.filemaker > #2223

Re: Changing to a Different Related Record

Show key headers only | View raw

In article <1m379e8.18o7x4015vmpluN%csampson@inetworld.net>, Charles H.
Sampson <csampson@inetworld.net> wrote:
> Helpful Harry <HelpfulHarry@BusyWorking.com> wrote:
> > In article <1m34ji3.pa6vtn1i5vevhN%csampson@inetworld.net>, Charles H.
> > Sampson <csampson@inetworld.net> wrote:
> > > 
> > > I've got a database in which I can't change to a different related
> > > record once a record has been committed. Think of accounts receivable
> > > where you've entered the wrong customer name.
> > > 
> > > Whenever I change one of the portal fields, I'm modifying the related
> > > record instead of changing to a different one.
> > > 
> > > I seem to remember doing this before but, if so, I've forgotten how.
> > > 
> > > I can create a new record with the related record that I want and then
> > > delete the record that has the related record that I don't want, but
> > > that's error-prone and clumsy. I hope there's an easier way.
> > 
> > You would need to change the data in the related record's link field,
> > which may or may not actually be accessible via the Portal.
> > 
> > Changing the customer name may not automatically change the link
> > field's data. For example the link field might be auto-entered data
> > based on the customer name, but either not able or not set to update if
> > the customer name is changed later.
> 
> I'm not following this time, Harry. In my case, there's just a simple,
> one-field, linkage between related records. Suppose I have a very small
> business which has led me to make the foolish mistake of linking orders
> to customers through the customers' last names. The behavior I'm seeing
> is that when I try to change to a different related record by typing a
> different last name over the original last name, FMP is changing the
> last name of the original related record.
> 
> As with accounts receivable, the relationship is many-to-one.

Portal fields are simply displaying related record data, so if you
change the data in a Portal field then it will change the related data.
If that field is also the link field for the Relationship, then
changing it will change which Parent record it is related to and
(depending on the relationship definition) usually disappear from the
current Parent record's Portal.

OR, it's possible from that description that you've perhaps got the
Related link field on the main area of the Layout (instead of the
Parent link field) - changing data in that would change the FIRST
related record's data.

I'm not sure, but it sounds like you may be trying to change a field
outside the portal so that the Portal then displays different related
records. To do that the field would need to be a Global field and the
Portal using a Relationship defined with the Global field as the Parent
Link Field.

Helpful Harry   :o)

Back to comp.databases.filemaker | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Changing to a Different Related Record csampson@inetworld.net (Charles H. Sampson) - 2015-04-19 11:58 -0700
  Re: Changing to a Different Related Record Helpful Harry <HelpfulHarry@BusyWorking.com> - 2015-04-20 09:02 +1200
    Re: Changing to a Different Related Record csampson@inetworld.net (Charles H. Sampson) - 2015-04-20 23:14 -0700
      Re: Changing to a Different Related Record Helpful Harry <HelpfulHarry@BusyWorking.com> - 2015-04-21 18:42 +1200
        Re: Changing to a Different Related Record csampson@inetworld.net (Charles H. Sampson) - 2015-04-21 13:25 -0700

csiph-web