dvergin says much that is wise. I have a few other points to make:

• Stop using cgi-lib.pl before you become too familiar with it. You just cause yourself that much more pain the day you migrate to using the CGI module, which can be used in a procedural manner, no need to dip your toes into OO-water if you feel you aren't ready for it. Everybody generating web pages with perl knows about CGI.pm, and you have much experience to draw upon. Hardly anyone these days knows much about cgi-lib.pl apart from the fact that it is Bad and should be avoided.
  
  
• Don't name your subs Sub1, Sub2 ... SubN. Sure, it makes it easy at a glance to count how many distinct subroutines you have written, but that kind of information is not important. How do you know at a given moment whether it's Sub23 or Sub3 that you should be calling. Give them discriptive names that describe what they do. They should do only one thing, and do it well, so it shouldn't be too hard to name them.
  
  
• Don't call subroutines like &this(). Drop the ampersands and call them like that(). This actually has an important semantic difference, one that could possibly trip you up unless you know what you are doing. Dropping the & will make this work the way you expect when subs call other subs.
  
  
• The code if (@lineDB eq =~/$item\/t/) is not legal perl. If you are looking to see whether a scalar contains the value of $item followed by a tab, then you would write

    if( $var =~ /$item\t/ )
  [download]

  On the other hand, if you want to see whether an element of an array contains the value of $item, then you have to use the grep operator to apply the test to each element in turn:

    if( grep { /$item\t/ } @arr )
  [download]

  Of course if you only want to check the first element for this possibility, then you would use the first example, with something like if( $arr[0] =~ /$item\t/ ) which I think is what you really want.
  
  
• Storing information in flat files works quite well, you don't always need a relational database.
  
  

Have fun

--

g r i n d e r
print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.