Thanks to all who took their time to try to help; especially since my OP does NOT provide an SSCCE nor all the other info that would be helpful. So...

Replying to the questions above in the order they were asked.:

  1. LanX: Execution and error names not match?
    ww: I have no clue but assure you, that's exactly what's happening. FWIW, there has not been a file with the name in the error on my machine since shortly after it was created and failed. (Yeah, I know, I should use some sort of version control. Bad on me!)
  2. LanX: shebang....
    ww: For all practical purposes, windoze ignores that shebang, but ultimately, execution will be on a Linux box (Apache).
  3. LanX: try....
    ww: Good thought, but basicly, I couldn't do that. see first ww reply.
     
  4. beech: use code on PM site? (1)& (3) "$select" error
    ww: Great idea, but failed because I'd removed too much code in effort to be (most of) SSCCEE.
    However, after downloading the PM code and restoring what I'd removed, I found a what I think was one problem; the quoting at what became line 50 was INCORRECT. It used single quotes inside the curlies, rather than escaped double quotes.
    beech: 2: vers?
    ww: 5.24, ActiveState, on dev box, Win7 pro (which harbors an evil spirit of some sort; see first reply to LanX.)  
     
  5. Marshal: (as ww understands question) re "invalid statement before the skedhash assignment"
    ww: Some fields in the db are null; I got tired of double checking which were generating the warnings.
    And if the discomfort is about the %skedhash = @_, the sub is being passed a hash, %skedrow.

I hope I've also learned something else: Don't post a question at near-midnite, Christmas nite (or any other nite). Sleep on it! I suspect (suspect!) I have now solved the actual-misleading-weird-messages-issues with your help and a variant of the teddy-bear method. Again, thanks, and when I'm confident of the solutions, I'll update with (too much) actual, working code

++$anecdote ne $data


check Ln42!

In reply to Re: runtime error not caught by compilation check??? by ww
in thread runtime error not caught by compilation check??? by ww

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.