> I have a well functioning split, secured, multiuser app with Tony
> Toews autoFEupdater running.
[quoted text clipped - 6 lines]
>
> Jesper
There are some differences in the runtime. An Access app built by a
seasoned pro that uses "best practices" throughout would likely execute
under the runtime with no perceptable differences to the user and with
little or no modifications required. An amateurish app built via the
wizards might not be usable at all under the runtime. So where between
these two descriptions your app falls is the relevant question.
Assuming a well-built app then yes, you could just install the runtime on a
PC along with your file and then just run it much as you do now. The
developer's tools will create a setup package to install both the runtime
and your app, but that would only need to be used once per PC. Future
updates would be a simple matter of replacing the file just as you would
with a licensed copy of Access.
What you need to do is find the help topic (should be available on
Microsoft's web site) that describes what the differences are in the runtime
and what changes you should make (if any). Also you can just test it on one
of your current PCs by creating a shortcut that opens Access and your app
with the /Runtime command line argument. This argument simulates the
runtime environment on a PC that has a licensed copy of Access installed.
Then you can see specifically what works and what doesn't. That shortcut
target would look like...
"full path to MSAccess.exe /Runtime "full path to MDB"
The short list is that the runtime has no access to the built in db window
and no access to any of the built in menus and toolbars so YOU have to
design in all of the tools that allow the user to interface with the app.
In addition, the runtime does not gracefully deal with unhandled errors so
all your code must have robust error handling. Where a licensed copy would
display a built in error message the runtime will just throw the user out of
the app. Because they lack error handling it is not a good idea to use any
macros in a runtime app (AutoExec and AutoKey should be okay if they don't
do anything likely to fail).
There is a small handful of features that the runtime doesn't support.
Filter-By-Form being one I can think of off-hand.

Signature
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jesper F - 24 May 2006 21:11 GMT
>> I have a well functioning split, secured, multiuser app with Tony
>> Toews autoFEupdater running.
[quoted text clipped - 9 lines]
> under the runtime with no perceptable differences to the user and with
> little or no modifications required.
Thanks for your detailed answer.
The app has all the necessary menus, interface and errorhandling and runs
well with the /runtime switch.
> Assuming a well-built app then yes, you could just install the runtime on
> a PC along with your file and then just run it much as you do now. The
> developer's tools will create a setup package to install both the runtime
> and your app, but that would only need to be used once per PC.
Since I'm using the AutoFEupdater I'm constantly copying the most recent
version of the db from \\share\db\mydb.mdb to
c:\db\mydb.mdb on the local pc.
I assume I would then have to make a installation package that installs the
Access runtime (AR) and a dummy db to C:\db\ just to get the runtime on to
each pc as I assume that it's not possible to simple install the AR without
specifying a db to be installed along with it?
And then in the future just let Tony's AutoFEupdater handle updates from the
network share.
Jesper F - 24 May 2006 21:49 GMT
> "full path to MSAccess.exe /Runtime "full path to MDB"
I'made an installation package including the ART and a dummy db.
However, the shortcut on the desktop that the installation package creates
simples says:
C:\...msacces.exe c:\pathtodb
Is the ART also called "msaccess.exe" just like the full version? (I believe
so)
It seems I still have the full version of Access runing on my pc, but if I
had done this procedure on a pc without Access maybe it would have correctly
installed the ART.
I guess I'll have to try on a pc without Access already installed.
Rick Brandt - 25 May 2006 01:06 GMT
> > "full path to MSAccess.exe /Runtime "full path to MDB"
>
[quoted text clipped - 8 lines]
> have correctly installed the ART.
> I guess I'll have to try on a pc without Access already installed.
The runtime is the exact same program. Just with (hundreds) of registry entries
that restrict full-blown usage.
You're correct that the package will not install the runtime if the same version
of Access already exists.

Signature
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jesper F - 27 May 2006 15:15 GMT
> The runtime is the exact same program. Just with (hundreds) of registry
> entries that restrict full-blown usage.
>
> You're correct that the package will not install the runtime if the same
> version of Access already exists.
Ok, I think I'm ready to do it then.
Thanks for your help.
Jesper