Normalize the data is something we are taught and usually, fail to do. Here you have done that and now you want to flat file it instead?
Only one note, address or person involved in a job? Maybe this is for billing a weld and not a bridge? On Fri, Jun 15, 2018 at 11:30 AM < [email protected]> wrote: > (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 > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYJPc2-RUt=0USRoC6Gm_xuOpRMH49eni2MLJ2LV4=D=y...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
