Best method handling Billto ID and shipto ID

[penwood]

I would like to see if I am doing this okay. I want to confirm the best manner of storing a BilltoID and a ShiptoId address.

I presently store 1,000 BilltoID's with 1 address each record in table1. Then I have 1,500 ShiptoID's with 1 address each record in table2.

I figure that i would make a main form with a pulldown combo box on the left for soldtoID and have an address travel in from table1. and then a different set to the right with another pulldown combo box for the shipto address pouring in from table 2.

I have looked at some models. they seem to have the BilltoID address is linked to a table1 like mine with one address in a combo box. However the Shipto address section in their samples is a Manual input section and not a table.

So is my method better? That is, using 2 tables and 2 combo boxes on the form.

Unrelated to my Order form, i want to mention that I also have a Contact table with many people who could get letters from us. so i have more address over in that table using 2 fields in this contact table (billtoID and shiptoID). therefore, this Contact table can be used for a subform and connect to a main form using those 2 fields as parent child thing.

thanks you for reading this and giving suggestions before i proceed.

 

[neileg]

It depends on your business model. In my experience, billing addresses rarely change. However, depending on the industry, one customer may have multiple shipping addresses, or the shipping address may change for many/all deliveries.

There is an argument that you should keep all addresses in one table with a field that flags whether it is a billing or a shipping address.