I have a table that contains several different classes of images. I need to mix various images into one record in another table - It is a product catalogue that shows interchangable parts of a finished product. Am I best to separate the various classes of parts (images) into individual tables and relate these to the completed product table or is there a way to collect the required images from one table into a single product record in another table? I have it working the first way but would like to simplify the structure and updating process.

Definitely do not separate the different images into separate tables. This will cause all kinds of headaches for you. Keep them in a single table and differentiate them with a category field.

You could use a multi-key to avoid creating a many-to-many relationship but it will make other tasks more difficult like populating the multi-key and reporting. I think you are better off with a traditional join table for your many-to-many relationship.

Since it sounds like you may need some help with the concepts behind a join table, I have referenced an invoicing solution that demonstrates a standard many-to-many relationship. Hope it helps.

http://www.filemakerpros.com/joinprint.zip

thanks John - that is mint

Edited October 18, 200619 yr by Guest