Target is not part of a related table

[Carl Smith]

As part of a startup routine I have a script that sets values, using the Set Field step, to certain global fields across all the tables of a database (e.g. Constants, etc) which has been working fine since I built it, but I recently added a new table and added a new set field step to this script and now when the script runs it is showing Error Message 103 and a dialog with the text "This operation could not be completed because the target is not part of a related table".

I can't initially see why there has to be a relationship in this instance as the fields should be being populated in the background.

Can anyone explain the logic here?

[bruceR]

In the background? What does that mean? There is no such FileMaker terminology. You've already got your answer, from the error message. You must have a relation to the target field, period. EIther because it is in the table directly associated with the current layout; or because it is in a related table.

[LaRetta]

Hi Carl,

You can set globals in any table without requiring a relationship. As Bruce indicates, your post is a bit confusing but the first thing I would check is that the new global in the new table is indeed set to global. Otherwise, you'll get this kind of message when you attempt to set that field. Just a thought! :wink2:

[Carl Smith]

Hi

Thanks for your replies. Please excuse my terminology (background = behind the scenes - i.e. tables not presented to the user).

LaRetta, your suspicions were correct the field was incorrectly defined. Now I know something else about the workings of Filemaker that, sadly, doesn't seem to be covered by their own Tech Support.