I've run a Filemaker solution for years that has multiple tables related by one field (Asset Number). Thus, all of the data from the various related tables connected by this one field. The customer wishes to change to having Serial Numbers (a field we've gathered for years) as the key relationship. However customers will still submit their data based off Asset Number.
So my question is can I safely have two fields with relationships, and do so without destroying/compromising the relationships already in place. In a nutshell, we need to allow data to be related by both Asset Number or Serial Number.