For the price we are paying , it shouldn ' t come like that <| sep |> This is my smoke spot ! <| sep |> Which I think makes more sense because a Torontosaurus sounds like they ' re the Toronto TRex ' s <| sep |> I ' m a simple man . I see unnecessary hate , I downvote . <| sep |> You just described this server <| sep |> Wow quick response ! Thanks for taking the time to help ! I suspected I ' d need a line item table to resolve the many to many relationship issue so that confirms my thoughts . I think I may get around the issue of multiple invoice addresses by using a ' sent to ' type of field with the various addresses as an option in the INVOICE table and using the ADDRESS tables ' ' main address ' entry as the the address written on the invoice , as ultimately the invoice is related to that account and is the responsibility of the account holder to pay me ! That would solve the issue of invoices having many addresses I think as each invoice would still be related to a single ACCOUNT but would have ' ADDRESS account main address ' as the relevant address to the account . Oh and thanks for suggesting that I set up the relationships before honing the layout and trashing it when it didn ' t work . too late I ' ve already been down that road several times but at least it helped my learning curve seeing the mistakes in action ! 😉 When if it all works I think I ' ll feel pretty chuffed that I managed to do something that is very much outside my skill set ! Thanks again for the advice !