March 16, 200916 yr Hi, How would you design the relationships between customers, invoices and products where : A customer is member of a customer type. Each customer type can have different prices for different products. The image represents what I think would be a good beginning.
March 16, 200916 yr You need an unstored calculation field cCustomerType in InvoiceDetails, and make the relationship from there to ProductPrices match BOTH ProductID and CustomerType - otherwise you won't be able to lookup the correct price.
March 16, 200916 yr Author Yep, your right. I made up this one quite rapidly. I forgot this field and relationship.
Create an account or sign in to comment