Even in Ye Olde 5.5, you are not limited to a single relationship between files (tables).
I'm not sure if you are trying to match one value or two between your two tables. Is the unique part number truly unique? or can one "unique part number" actually refer to several blanks of different sizes?
If it's truly unique ( and it should be), then you simply need to define a relationship that matches the unique part number in both files.
PS. Microsoft is trying to phase out Windows XP so the day is coming when you might have a computer die and then be unable to acquire a machine that can run FileMaker 5.5. It's better to upgrade and convert a file as old of this before such an even occurs and you have to scramble to do it all in a very short period of time.
Yes, the unique part number is truly unique. :) Blanks have a one-to-many relationship with finished products, meaning that we use the same blank size for multiple finished products. Product plates have a one-to-one relationship with finished products, as each label can only have one product's information on it.
I'm trying to relate the unique part number of the finished product (PR 1215-60-0HLG) with the unique part number of the blank (Blanks-SS-0HLG) at the time of ordering (so that the print shop can use the correct pieces to make the finished product) based on the size and customer number of the finished product.
Sorry it took me a second try to eloquently ask my question.
I am pushing hard for a newer version, insofar as I called FileMaker Tech Support to make sure my files were convertable. Nobody but me understands the scope, nature, or difficulty of what I'm trying to do, though, so I may just throw up my hands and tell them the depth of versioning and record keeping they're asking a 10 y/o program to do is impossible unless we upgrade. Letting them know your PS may be helpful in convincing them...thanks!
OK, I mistook "unique part number" as the identifier for the blank, not the finished part.
Sounds like you need a unique identifier in the blanks table such as an auto-entered serial number. Then you could select a blank ID in your finished product table (or it could be auto-entered during data entry perhaps) that links it to the table of blanks info.
As to upgrade, just ask them to consider the cost of a business interruption if the hardware fails and you can't get back up an running by putting a back up copy on a new machine because it will no longer run your program. One of my selling points to my boss was to stress how much better a conversion job I could do if I did it in a carefully orderly fashion rather than by having to rush it all out in a few hours while our business was stopped cold for lack of computer support...