Using AutoFE Updater with Runtime Packages?

[markmarko]

Using Access 2007, we are deploying using Runtime packages, as none of the
client machines have the full version of Access.

Is it possible to use Tony's AutoFE Updater (
http://www.granite.ab.ca/access/autofe.htm ) with Runtime Packages? The issue
I see is that Runtime packages require installation, and in case a version is
already on the client machine, requires uninstallation of that app first.

Does anyone know how this might work? Or perhaps an alternative Auto FE
Updater option?

 

[Albert D. Kallal]

Sure, using an updater is a great idea this scenario.

Remember there's no special connection between the database files you copy
to that computer, and the installation of the runtime.

in other words what I do in most cases is simply get the runtime installed
completely separate of my application.

I then simply copy the mdb or mde (or in your case accDB/accDE) files to
that target computer.

The runtime is really essentially the same as the full version of MS access,
and once you've installed MS access/runtime, additional database files can
simply be placed on that target computer and they'll run.

I do believe because of a security or trusted location issue, you might let
the runtime install the first version of your front end, but from that point
on any updates is just a simple file copy.

 

[markmarko]

So If I just place the accdb file onto a machine that does not have the full
version, but has runtime, it will open using runtime? I was under the
impression that it was more complex than that, since the packager 'installs'
onto the client machines.

 

[Albert D. Kallal]

So If I just place the accdb file onto a machine that does not have the
full
version, but has runtime, it will open using runtime? I was under the
impression that it was more complex than that, since the packager
'installs'
onto the client machines.

The above is correct, you can simply copy files and place them
anywhere...even on the desktop.

when you double click on this file MS access will run and launch the file as
usual.

As I said there's no special connection between your database files and the
runtime itself. The runtime is quite large (55 megs??), and is simply a copy
of ms-access without designed parts enabled.

The only difference is you'll encounter between runtime and full version is
some built in menus etc. are not available.

Thus, as a general rule you have to provide your own interface for the user.

While most people install the runtime + their application at the same time,
there's absolutely no need to do so, and as I further pointed out there's no
special connection between the application you installed in the runtime. it
is just a regular access accDB file sitting on the hard drive...and double
clicking on this file will launch it as usual.

 

[markmarko]

Well, that's easy! And here, all this time, I thought the Runtime Packager
was something I needed in order to deploy to machines using Runtime.

Thank you very much for your help!

 

[×בי hgec]

×יפה יש קבוצה בעיברית