Database design

(VFP9SP2 app with MySQL backend)

Some years ago I had created a solution where I had split the main data table into 5 separate tables, each with a 1:1 relationship. I kept the commonly held fields in the table, and moved others off like so: - Main Job table - Job Address table (job site address) - Job Dates table (key event dates for this job) - Job Notes table (all text/memo fields, with key field of course) - Job People table (folks assigned to the job)

On review, I think this just made more work and I should consolidate all of these fields inside the single Job table.

Your thoughts on either design approach?

tia, --Mike