Context: Matchfield in a related file that is the same across all records to pull all records from one T.O. to another. One can do this with a text field formated to auto enter a data entry (eg: A) or a calc field with the calculation "a", and both set to save and index.

Question: is there an inherant advantage of one over the other. To my brain the calc field is nice in that if I decide to change the contents (for whatever reason), I don't have to do a find and replace as I would have to for the data auto entry.

Analogus issue: in the main file, I can use a global or calc field as a match field that is the same regardless of what record I am in but unique to each computer station on a network, (eg to make a relationship using the terminal name to pull the user's passwords, privileges, preferences...). Is there an advantage in using a setfield into a global for the MF or simply use a calc field (such as Get(UserName))?

In FMP 7 there is no need for this type of relationship. The X relationship does this.

In older versions I used the Calculation since the user can not change the value. Also don't use 1, use some random number.

What is the X relationship. When defining relationships one can look down the pop down list and see the =, unequal, <, >, and X. Is this "X" what you are referring to? If so, what type of field do I specify and how is this field formated in FM 7? Thanks.

Yes that is the one. Just use the key fields of the 2 tables. It will match every record.

The choice depends on whether or not you want the user to enter the field.

Will try it. Thanks.