Access wants to be a frontend. And it works pretty good as a frontend. The major problem with Access is the database used as its backend (namely, Jet). Even Microsoft wants to ditch Jet (but that'll take a while, due to legacy apps). It is possible to use Access to a frontend to other databases, including MySQL, via ODBC.
While better than Jet (which isn't saying much), MySQL has other problems. It implements the bare-minimum requirements to be relational, and transactions are only kinda, sorta working. At least it can keep track of its own mind, which is something Jet doesn't do.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
Note: All code is untested, unless otherwise stated
In reply to Re: Re: Compacting a MS-Access database from perl
by hardburn
in thread Compacting a MS-Access database from perl
by Grygonos
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |