I have made a database in A2002. I am looking to make a stand-alone
version that users with the runtime libraries can run. I also have
Visual Studio .NET 2003. As I understand, the Access 2003 Developer
Extensions is what I need to make this happen.
1. Are the Access 2003 Developer Extensions included in Visual Studio
.NET 2003?
No
2. Will the entire front end from the database (i.e. the forms, there
are no menus or toolbars) have to be re-made or can they be packaged
from the current mdb?
You perhaps have a bit of confusing as to what the runtime is. The runtime
is simply a cut down version of ms-access with the design tools removed. You
install this runtime, and then take YOUR EXISTING mde, or mdb file, and
simply place it on that computer (like you do now with the full version).
Double clicking on the mdb (or usually mde) will launch your application
Make no mistake here, this is large ms-access install, and it can often
occur separately from your mdb/mde file. Your mdb should run on that target
computer un-changed (expect for issues in your next question...see
following).
So, for example, the access 2000 runtime used to be 150 megs in size, and
often required a re-boot of the machine during installing. This is not some
small package here. The end user will need the same permissions and issues
exist in installing a copy of ms-access. And, since the runtime is
compatible with the actual version, then you ALSO HAVE ALL of the problems
that exist when you try and install, and run multiple versions of ms-access
on the target machines.
Again, I can't stress this, but the runtime is large full ms-access type
install, and the ONLY thing missing is some features that allow you to
modify the forms.
3. The mdb is not terribly complex. How complicated will a
novice-to-moderate developer find this process?
As I said above, you don't actually modify your application, and the runtime
for all matters is really a separate install from your mdb. You do however
have to provide your own interface. So, if you need code to re-link tables,
or if any part of your application relies the built-in ms-access menus, then
you do have to provide those. However, if you have a main start-up form with
a exit button, that might be well enough. The runtime does provide a basic
file, edit menu.
However, if you reached the point of being ready to deploy your appcation,
then you likely long ago hid all of the ms-access stuff, and provided your
own menus + forms anyway. So, the issue of the runtime being more work is
much moot here, since if your appcation REALLY is ready for your end users,
then you been running an application that hides the ms-access stuff for
likely a very long time anyway....
The runtime is really just a ms-access install. You just don't get the menus
to modify things. So, your mdb file does not under go any changes, and you
simply copy your mde, or mdb files to that computer, and double click on
them to run.
If that target computer will already have a different version of ms-access
installed, then again you will be creating a bit of mess, all of the
problems of installing two versions of ms-access on a machine remain as
before, and of the problems of more then one version will exist (as I said,
this really is much like a regular ms-access install).
