I take it that you have:
Customers----<Projects----<ProjBOM>-----Parts(Products?) (---< means "one to many")
Am I correct that each user will have their own favorites list?
If so, add these relationships:
Projects::cAccountName = FavoriteParts::AccountName
FavoriteParts::PartID = Parts 2::PartID
For more on this notation, see: Common Forum Relationship and Field Notations Explained
Make cAccountName an unstored calculation field that returns text: Get ( AccountName ). Make FavoriteParts::AccountName a text field and enable "allow creation of records via this relationship" for parts Parts 2 should be a new occurrence of your Parts table.
And you can set up this portal so that clicking a button in the portal row will add that item to the BOM table.
Yes, each user account would have their own favorites list.
I will give this a try. One question though....Won't this setup limit the favorites list to favorites that are related to a specific project? If so, I would like the favorites to be both project and customer independent.
The relationship matches strictly by account name so the particular project record that is current has no effect on what related records are present. But make sure that cAccountName is an UNSTORED calculation field or this won't work.
Thank you very much. That works perfectly!