Thanks for the comments. It gives me a direction to go in. Since this is really a side project, I'm not devoting a lot of time and energy to it, but it will be helpful in the near future because we have a lot of data to crunch from log files.

Here is a sample of what the data might look at in its rawest form (note, the data looks slightly different depending on its source, W2K or Unix).

__DATA__ Field1=Value1,Field2=Value2,Field3=,Field4=Value4 Field1=Value1,Field2=Value2,Field3=,Field4=Value4 Field1=Value1,Field2=Value2,Field3=,Field4=Value4
And so on. The Field names might look slightly different depending on the originating platform. I'm sure there is a better way to do this, but I'm still learning.


"Ex libris un peut de tout

In reply to Re: Problem with strict "refs" by nimdokk
in thread Problem with strict "refs" by nimdokk

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.