Yeah, that's kind of what I was thinking. It has the added benefit that the user (there's only one) can just keep using the interface that she's comfortable with.

This would buy me time to rewrite the GUI in Perl/Tk. Of course, any new feature requests would be developed for the new GUI, giving her an incentive to switch :-)

I'm really intrigued by dwildesnl's thought on turning it into a web-based app, but I'm more comfortable in Perl/Tk - especially as I hope to have a quick turnaround time on this.

Perhaps for some of the other apps... Time to do some research!

In reply to Re^4: Converting Microsoft Access to Perl/Tk/DBI by bibliophile
in thread 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.