Table structure - multiple locations

[pwicr]

I have a number of dealers:
each of these dealers has multiple locations.

Right now they are each set up in the same table with each location as a separate dealer.

ex.
dealer1 - locationA
dealer1 - locationB
dealer1 - locationC

They have a number of different fields...one with the long name with the dealer and location all in one field so that I know which is which, and a short one (dealer1) so that if I do a query just typing in "dealer1" it brings up all locations.

Is there a smarter/easier way to do this?

 

[John Big Booty]

You could move the dealer addresses to a sub table. Your table structure might look like;

TBL_DealerHdr
DealerID (PK)
DealerName

TBL_DealerLoc
DealerLocID (PK)
DealerID (FK)
DealerAdd


PK = Primary Key
FK = Foreign Key