Esteemed Monks,

I've recently been handed a crufty old (well, MS Access 2000) Access db application to maintain.

As this is a little-used app, I thought I'd take the opportunity to rewrite it in Perl/Tk/DBI (probably MySQL as the backend)... purely as a learning excersise.

I see three paths to follow, here:

  1. Dump the data from Access, load it into MySQL, and point the Access front-end to the new backend. Then rewrite the front-end in Perl/Tk.
  2. Rewrite the front-end in Perl/Tk, and use DBD::ODBC to get to the data. Then convert the data to MySQL.
  3. Do both at the same time (basically, just rewrite the app from scratch).

Has anyone here had any similar experience? Recommendations? Red flags over looming snake-pits?

Basically just looking for opinions :-)

In reply to Converting Microsoft Access to Perl/Tk/DBI by bibliophile

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.