You say there is one result, but the evidence (an undef being returned) indicates that there is not.
If my $result=$in->next_result; is putting undef into $result there must be a reason for it. The key is figuring out what that could be.

Since $in is a new Bio::SearchIO(...), you should look at that documentation to find the conditions under which next_result will be undef.

I could guess and suggest that perhaps your file is empty, does not exist, does not have permission for you to view it, or even contains data in the wrong format.

PS:
Out of curiosity, why are you prepending ">" to the filename you are passing in? It seems unlikely that that would result in a valid file name.

In reply to Re^3: I don't understand error message by SuicideJunkie
in thread I don't understand error message by lomSpace

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.