Here is a random opinion.

In my experience Microsoft Access in multi-user mode has some nasty race conditions. Put it under load and it will randomly lock up and fall over. That would make it significantly less robust than MySQL.

If you value standards compliance, MySQL wins over Access. (eg Should like use a * or % as the wildcard?) Likewise MySQL does not tie you to a specific OS platform.

I have no idea which has a better optimizer. I am certainly unimpressed with the Jet engine. But I've never thrown complex queries at MySQL, so I can't say how it compares.

But on features, I'd suspect that Access wins. If not in features that I care about...

In reply to Re^3: Drowning in Modules - Suggest those for DB App by tilly
in thread Drowning in Modules - Suggest those for DB App by KevinR

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.