I don't quite understand your terms, but I think I would set it up kind of like an invoice solution
Then in it's simplest form, you would have a portal on the sample record for SampleParameters, where you can select the SampleParameters by calculation or lookup. The parameters table would be a list of every type of parameter. If certain locations always require the same SampleParameters, you could auto populate them by script.
You would also have a dropdown based on locations, to select the location
Thanks, Steve. I honestly hadn't thought to approach it that way having a separate Sample table like that and then having the join table.
Just so my head is straight on this, the Sample table would then have all samples taken for that instance in one record and be associated by the sample number or id, correct?Never mind, I see where I looked at that incorrectly now. I'm going to go check out an invoice solution to get a visual as well. Thanks for the suggestion.
Yes one Sample record would show like an invoice. One sample record would be an instance (record) of one sample taken, at a specific location, at a specific moment in time, with the sample parameters (lineItems) in a portal. Those sample parameters would be looked up/added by calculation/script, from the Parameters table.