What does this odd behaviour mean?

[Clare]

Hi everyone,

I have a question regarding strange field behaviour that I've seen a couple of times. I'm quite sure that it's a result of one of the many gaps in my filemaker knowledge and I won't go into detail because I'm certain someone will recognise the symptom...

Basically, I when I fill out a field in a portal row it seems to fill out for *all* records, depending on which table occurence the field is directed to. Or just fills out the one field but where that record should show up in another portal (via a relationship based on the problematic field containing that value), a different record appears instead of the one that should.

I'm a little shaky on which table occurence I should be using here, perhaps the problem lies with that.

Wisdom appreciated! If no one can help and I can't figure it out I'll be more specific.

Cheers!

[Wim Decorte]

It would seem the relational setup is not correct, but we can't offer any good advice without seeing the graph and some explanation of what the solution is about.

[Genx]

... no, the problem is very likely to be that the field you've defined in your portal is pointing to another Table Occurance... point it to the same Table Occurance as the portal and im fairly sure this will fix your problem, otherwise do as wim suggests and post a screen shot of your relationships...

...or else its your portal thats pointing to the wrong TO...

~genx

[Clare]

thanks guys, yes it was to do with pointing to the wrong TO... i got caught up in worrying that two different text entry boxes for the same field had to use the field from the same table occurence in order to look at the same data. but of course you can access the data in a given field from any occurence of the same table, right (unless it's set otherwise)? so i could set the field TO to suit the portal and it's all good now.

thanks again!!