Free DB better than Access: Mysql and PostgreSql. Check out freshmeat.net.

If you want a quick windows like ap, vb it.

But I can tell you I built a timesheet app for a 30 person company based on Apache and Perl, and I did it because when they asked for it to be based on Access it wouldn't hold up. So I moved it to mysql on NT and then mysql on linux, last week. And new apps and functionalities get requested for this intranet system which can all use past code.

The worst case scenario, I met a sysadmin for a big bank who had programmed everything in access and when he wanted to get away from Microsoft everything and go open source, it just couldn't be done without rewriting all the logic and everything. DB-agnostic, platform-agnostic, and flexible, that's Perl.

I wouldn't use compiled Perl. Probably you should consider what the company is going to be doing in the future and especially if there seem to be things that Perl is good at coming into the project in a later part of the game. I just have had experiences getting painted into corners in VB (though it has gotten better since then) while I know it is very likely I'd be able to do what I need to know if it's in Perl. 'Course how about Java?.. Move SIG!

In reply to Re: Is Perl the right solution... by mattr
in thread Is Perl the right solution... by Lord Wrath

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.