Ok, thanks.
I was under the impression that there is a very solid underlying datamodel, which is excellent. And that this datamodel allowed for having an option, say in the case of guitar: finishing in gold, silver or bronze, which will differ in price depending on the type of guitar, for instance bass or electric, electric or acoustic. And many other options such as type of hardware, pickups, etc. And the only think differing is the price. It would be so much less maintenance if I had been able to only register the gold, silver and bronze finish once, and add the say 100 guitars once. And that the options when used for a particular type of guitar just got a different price. That way I would only need to add those three options, and 100 guitars, and add the price only to that relationship. If I understand you correctly, I will now need to create 300 options instead of 3. Namely gold-guitar-1, silver-guitar-1, bronze-guitar-1... then gold-guitar-2, silver-guitar-s, bronze-guitar-2, each time with the prices. So I will have 100 guitar products and 300 options to maintain, instead of 100 guitar products and 3 options.
This creates a tremendous amount of work, I hope you can have a look to see if this can be looked into to simplify this so that instead of maintaining 300 options here, we can just revert back to maintaining the three options with the price being determined on the relationship between guitar and finish-option.
Alas, for now I will have to do it the cumbersome way I fear. 
Thanks for advising.
Cheers,
Marjoline