I did this once with UDF fields and scripts.  I had a separate UDF for each Product type's linked field values.  Using your example, I had UDF_Apple_Color, UDF_Pear_Color, etc, and each one had it's own list of color values.  With scripts, I used oScript.SetUIControl to show the correct UDF when the Product type changed, i.e. when Product Type = "Pear", show UDF_Pear_color and hide the rest.  The script also copied the value from the Color List into a Color Text UDF, which is the field that can be used in reports (so the color value is in the same field for reports.)

This was a good option for the company because their Product Types were static and they only had about six  The values of the color lists could change, so we used UDTs for those.  If your Product Types change a lot, or you have too many of them to create UDFs for each one, this wouldn't be a good option for you.

That's a creative way to accomplish it. I think we may have too many values for UDFs. I'm thinking I might just have to have one long list and multiple attribute UDFs (attribute1, attribute2, attribute3, etc) maybe up to 10 or something. There isn't a good "one to many" solution in Sage 100 without hiring a master developer.

That's a creative way to accomplish it. I think we may have too many values for UDFs. I'm thinking I might just have to have one long list and multiple attribute UDFs (attribute1, attribute2, attribute3, etc) maybe up to 10 or something. There isn't a good "one to many" solution in Sage 100 without hiring a master developer.

Have you looked at Bill Options?