The runtime system is actually installed to the SAME file and dir location
as the full edition.
In fact, if you have the full edition of ms-access, then installing the
runtime does absolute nothing (be thankful..as you would not want to over
write the full edition of ms-access).
The runtime edition of ms-access is NOT any different then the full edition
with the exception of the design tools removed. So, you don't "run" the
runtime.
The way you run your applications in a runtime system is NOT different then
the full system.
To run an mdb, or mde file, you :
1) install full edition of ms-access, or runtime edition
2) double click on the mde, or mdb file to launch it.
Note in step #2, there is NO difference here between the full edition, or
the runtime edition. Make NO mistake here, the runtime is simply an edition
of ms-access and it will launched when you double click on a mdb, or mde
file (the file is launched based on the file extension....the runtime works
no different this way is not somehow attached to ONE particular mdb or mde
file).
So, after you installed the runtime, you can then copy as many mdb or mde
files to that computer and double clicking on those files will launch
ms-access (in this case the runtime edition).
As mentioned, if you have the full edition of ms-access, then installing the
runtime edition DOES NOTHING since ms-access is already installed.
However, for testing and viewing what your application will look like and
run like in an runtime environment WHEN you have the full edition, simply
use a shortcut to msaccess with the /runtime switch.
This you use something like:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"
"c:\program files\RidesXP\RidesXP.mdb" /runtime
You can read the following article of mine that explains this issue here:
http://www.members.shaw.ca/AlbertKallal/RunTime/Index.html
The above is for 2007, but the same rules apply...
