One good/possible solution is to have two versions, one with the runtime,
and a 2nd one without...
the runtime for a2000 was up to 150 megs in size at one time.
However, the a2003 runtime is a reasonable 34 megs in size (I say
reasonable, since the .net runtime is about 22 megs in size also).
It is not clear what version you are using, but from memory:
a97 14 megs
a2000 up to 150 megs, and re-boot of machine
a2003 34 megs
Of course, you do realize that the runtime is really like installing a FULL
version of ms-access on the users machine. That means all of the SAME
complications and difficulties will occur if you install ms-access (or
runtime) on a machine that ALREADY has an version of ms-access. this will no
doubt case you to spend much time on support calls...often, this type of
support can eat up any profits on the product sold.
So, I assume you have the support and infrastructure in place to send users
updates to their software (again, without the runtime included), and I also
assume you taken steps for those users will install ms-access (or the
runtime) on machines that *already* have a version of ms-access. there is a
CONSIDERABLE number of problems, and just basic obvious ones like which
version of ms-access will be used when a user clicks on a mdb file after you
install YOUR runtime? (you can WELL see how this will mess up a clients
machine with GREAT ease).
It is assumed that you spend considerable time and efforts dealing with
multiple versions of ms-access being installed. And, that you take
precautions for users that would out of the blue installed HUGE product
like ms-access on their computers.
you do realize that the runtime is the same as the full version, but ONLY
with design features removed? So, those users need to be informed that they
are installing a big version of ms-access, and that this will potentially
cause many problems if they are using a current/existing version of
ms-access...