First off all I suggest you to use HTML::Template or one of the other popular templating systems to separate code from content. You print a table for each record you receive - maybe it would be better to print just new table-rows for each of them. If you want your users to be able to edit those recordsets again you could create a html-form for each recordset, display them in input-tags and add a submit button. Based on the action you receive via CGI your script will display/add or edit records.

UPDATE:

An example CGI app of my own to show you a way to structure such an app:

#!/usr/bin/perl

use strict;
use warnings;
use CGI;
use CGI::Carp qw ( warningsToBrowser fatalsToBrowser );

use DB::Countries;
use Templating::Countries;
use Query::Countries;

#
# declaration
#

my $q = new CGI;
my $form = $q->Vars();
my $db = new DB::Countries;
my $tmpl = new Templating::Countries;

my $dispatch = {
  'search'  => sub { my $query = new Query::Countries ($form);
                     $tmpl->overview($db->get($query));         },
  'edit'    => sub { $tmpl->edit($db->get($form->{'id'}));      },
  'new'     => sub { $tmpl->add();                              },
  'delete'  => sub { $tmpl->del($db->get($form->{'id'}));       },
  'update'  => sub { $db->update($form); $tmpl->default();      },
  'insert'  => sub { $db->insert($form); $tmpl->default();      },
  'remove'  => sub { $db->remove($form->{'ID_country'});
                     $tmpl->default();                          },
  'default' => sub { $tmpl->default()                           },
};

#
# main
#

print $q->header();
print $dispatch->{$form->{action}}
      ? $dispatch->{$form->{action}}()
      : $dispatch->{'default'}();
exit;
[download]

You can see that the app is reduced to a dispatch and just a few lines of code. Everything else is seperated in modules. One for all database-action, one for building queries and one for the templating. Based on the $form->action it receives it calls the related actions using the dispatch table.

---

---

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.