Do you see something WRONG with that code?

I consider that not using query parameters is wrong, but that probably has nothing to do with the problem you're seeing.

The only way you should see "1000%" is if you fetch a row whose "utype" field doesn't start with "i" or "h". How certain are you of your data? Are you sure that some fields don't start with "I" or "H". Or are some "s" records sneaking in?

A quick-and-dirty way to get some visibility onto the problem is to add 

  $html_content .= "<!-- " . $aff_row->{utype} . " -->";

[download]
after you fetch the row. Then, you can view the HTML source to see what you really got.

Dumping diagnostic info into HTML comments is a trick you can get a log of leverage from.

Update: You're generating bogus HTML, but that's a separate issue. Emit </td>, not </td />.

In reply to Re: Troubleshooting help... by dws
in thread Troubleshooting help... by powerhouse

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.