When designing a database, think of it this way:
The "kinds of things" that you need to keep information about would map to
the first cut of what tables you need. So if you keep information about
Companies and Cities, you need (at least) the tables Companies and Cities.
Keep information (attribut
Hi Andrew,
You don't need to use seperate tables for each company. In fact you
shouldn't since select queries with index are fast.
I suggest,
1 table for the cities at least two columns, one for a unique column with
autoincrement(cityid), the other is the city names, with appropriate column
types
