A Many-To-One relationship is the just opposite of the One-To-Many relationship. It is not any different programatically just different to think about. It is like a Child-To-Parent relationship.

Set it up exactly as you would any One-To-Many relationship.

Does anyone know if there's a way to create a many-to-one relationship? I want to create duplicate records in another database file while maintaining the information in each original record (in other words, I want to be able to create duplicate records in the original database file and append the contents of up to three fields in each one).

I just realized that I don't think I phrased my problem correctly. I have three files, Part Entry to enter the individual parts we use in production, AssemblyPartJoin to establish a many-to-many relationship between Part Entry and Assemblies, and Assemblies to show each assembly with a portal to AssemblyPartJoin that lets me enter the parts that belong to it.

In Assemblies, I have a checkbox field with the three models (finished goods) that we produce. Each record in Assembly reflects a subassembly that is part of one or more of the three models. Since there is a record in AssemblyPartJoin for each part number with the assembly it belongs to, I want to be able to export the information in the checkboxes to show which model the individual parts belong to in a field in AssemblyPartJoin. This will hopefully let me generate a report called Bill of Materials that will sort the records in AssemblyPartJoin by Model, then Assembly, then by parts in each assembly.

The functionality of checkboxes seems limited, so I created a string with spaces and used the LeftWord and MiddleWords functions to extract the values to three separate fields in Assemblies. The only thing I can think of doing with the information is to have each of the three fields create duplicate records for each part, listing the different models, in AssemblyPartJoin.

Is there an easier way to get the job done? I'm new to FM and open to any suggestions that might help in any step of this process!

-Brian