4 Tables or 2?

Should I split these up or?

[ramoneguru]

I have 2 tables (Schools, Districts) both entities have a mailing address and a physical address.
1. The person using the db isn't SQL proficient.
2. I'm dealing w/ about 12,000 records.
3. Ease of use would be better than efficency in this case.

Now would it be wise to have just 2 tables like MailingAddress and PhysicalAddress to store the phys/mail addresses for both Schools/Districts
OR
Would it be better to split it into 4 tables:
SchoolMailAdd
SchoolPhysAdd

DistMailAdd
DistPhysAdd

What's been your experience?
--Nick

[omoutop]

Keep the two original tables (Schools, Districts).
At my opinion its better to store data for a particular job in its own table.

There is a possibility to merge the 2 tables to 1 (depends on how many columns each table has). If you have many common fields, perhaps this method is more suited to you (and add a new field, something to store the Schools or Districts flag).