Your latter idea, assigning ID numbers to people, having "number,name" in one file and "date,number(s),hours" in the other file, is definitely the way to go. This is called normalizing a database -- basically, don't store a piece of "mutable" data in more than one place.

For that matter, don't store more than one name/person-number in a single "hours" record: i.e., it should always be just "date,person_number,hours", one person mentioned per row.

As for better suggestions, try actually using a relational database (e.g. mysql), where this sort of thing is quite natural and easy. (But that's not essential -- for something on this scale, you could just as well use perl hashes to provide the same functionality without breaking a sweat.)

In reply to Re: Changing records by graff
in thread Changing records by arrow

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.