I've got a direct relationship based on four fields. The relationship is valid after I fill in all four fields, but related fields on the layout do not fill in immediately, not even when I exit the record. However, they do fill in if I close the file and open it again. There are other circumstances where the fields show their proper data, although I haven't isolated exactly when this is. For instance, while I was investigating the fields and relationships, when I went back to the layout, the fields were filled in.

Has anyone else experienced this? I'm using FileMaker Developer 7.0v2, but the behavior is duplicated in Pro.

Thanks,

Chuck

Are the fields all text, calculation, what exactly?

I think I figured it out, at least part of it. Three of the fields are calculations that are based on related data from another table. The user doesn't edit these fields, of course, they edit the local fields that complete the relationship to that third table. If the user fills any of these fields last of the four, the relationship doesn't update properly. One of the match fields for the relationship that isn't filling in immediately is entered directly by the user. If this field is entered last (or edited after the other fields have been completed) the troublesome relationship immediately updates.

So what we have is four fields that the user edits. Three of them create a valid relationship to other tables, which completes three calculation fields that are then used as match fields to another table. FileMaker is apparently unable to update the calculated key fields when they are based on related data (perhaps because they are unstored?) and immediately complete a relationship based on those key fields.

I don't recall if this was a problem in Pre-7 when relationships could only have a single match field, so calculated multi-keys were the norm. I'm going to try creating a multi-key and see if that has better luck updating, although I doubt it will help, since, if my theory is correct, the problem will be the same (key field that is a calculation based on related data).

In the mean time, I've placed a button on the layout labeled "Refresh" that simply enters preview and then browse mode, and this forces the data to appear.

Any other thoughts on this would be appreciated, as I find the Refresh button quite a kludge.

Thanks,

Chuck

Hi Chuck,

I would bet that part of the answer is here

Chuck said:

The user doesn't edit these fields, of course, they edit the local fields that complete the relationship to that third table.

"local fields".

When a relatonship is based upon a Left calculated key, which value is evaluated using a distant "global", the related records would not update.

I have the feeling your situation is not that different, even if you didn't indicated the use of a global, and this situation appeared in pre-7 versions.

So what happens if you build your Left Key using local scripted "sub" keys, how exactly do you fill these "local fields" ?

Three of the key fields that the relationship is based on are calculation fields that are based on related data. This is where the problem seems to lie. The calculations get updated, but the relationship that is based on them doesn't. I've found in the short term that the Refresh button is satisfactory.

Thanks,

Chuck