Hi Lee Glad you got this working.
But that's no excuse for not reading and understanding what John wrote -- as quoted below :) This is important because it demonstrates one area where FMP7+ offers advantages to a developer over FMP6. Basically, you do NOT need a calculated field to achieve your aims here. That makes for fewer fields (easier management) and a clearer structure. Instead of a calculated field [FieldA & " " & FieldB] as we were accustomed to use in earlier versions, you can now simply add the two fields as keys within the relationship setup: FieldA::FieldA AND FieldB::FieldB You will find this pretty useful as you develop in FMP7+. Steve On 15/2/08 07:13, "Lee" <[EMAIL PROTECTED]> wrote: > Hi, > I haven't found the reason why but I deleted the relevant table and re > created it, the self relationship is now working with a calculation as > the key. > No idea of the difference in the two tables, however its working so I > guess I shouldn't worry. > > Lee >> >> John Haley wrote: >>> I am not sure why what you are doing doesn't work, but can you just >>> use both the fields separately since you can have multiple keys in FM >>> 8.5?
