Access 2007 Runtime vs. Full Install

[Scorp16]

A previous post got me to rethinking my Access upgrade plan.

Our group -- 60+ users -- currently use Access 97 for a number of databases.
All the users need to use Access (input / change data, reports, etc), but
only a couple of users of this group need to be able to modify the forms,
tables, etc.

Questions:
1. Should we be thinking about using the free runtime version for all
non-modify users?
2. Can multiple users use the same database via runtime with no issues?
3. Are there any known issues or drawbacks to using runtime (faults,
erorrs, etc)?

My employer is not worried about spending the money, he only wants a
seamless upgrade to Access 2007 with no change in functionality by the users.

Thanks!

 

[Douglas J. Steele]

Yes, you can use the free runtime version for al non-modify users.

That having been said, you should never have multiple users using the same
database, whether they have the runtime or the full version. All
applications should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables and relations). Only the back-end should be on the server: each user
should have his/her own copy of the front-end, ideally on his/her hard
drive. You may want to convert the front-end to an MDE (or ACCDE), but
there's no point converting the back-end.

 

[Scorp16]

Great Info Doug. Further questions ..
1. if the databases are split (front / back end), can the front end user
use Runtime (with no issues) ?
2. If the users each have a copy of the 'front end' on their computer, how
would I be able to easily make updates to the forms, etc (which I do often).

 

[Douglas J. Steele]

1. Yes.

2. You replace everyone's copy of the front-end as required. Tony Toews has
a free Auto FE utility that you can use to simplify this. See
http://www.granite.ab.ca/access/autofe.htm

 

[Klatuu]

--
Dave Hargis, Microsoft Access MVP

Great Info Doug. Further questions ..
1. if the databases are split (front / back end), can the front end user
use Runtime (with no issues) ?

Each user will need to have the runtime installed on their computer
regardless of whether it is on their hard (where it should be) drive or on a
network drive.
When you run an application, you are running it on your local computer
regardless of where the file is. Remember, Access applications are not .exe
files. You are actually running MSAccess.exe and it is uing the mdb, mde,
accdb, or accde

If you also download the developers tools for 2007, you can create an
Install package that will install the runtime on each user's computer along
with the accde you have created.

2. If the users each have a copy of the 'front end' on their computer, how
would I be able to easily make updates to the forms, etc (which I do often).

There are various ways to do this. One that I use you can get from this site:
http://www.granite.ab.ca/access/autofe.htm

It is free. What it does is compare the fe version number in a local time
with the current version number in a be table. If the fe is out of date, it
launches the updater and quits. The updater then renames the fe on the
user's computer and copies the new version from a specificed location on the
network, launches the new version, then the update quits.

The same functionality can also be done using a .bat file you call with a
Shell statment.

 

[Rick Brandt]

A previous post got me to rethinking my Access upgrade plan.

Our group -- 60+ users -- currently use Access 97 for a number of
databases. All the users need to use Access (input / change data,
reports, etc), but only a couple of users of this group need to be
able to modify the forms, tables, etc.

Questions:
1. Should we be thinking about using the free runtime version for all
non-modify users?
2. Can multiple users use the same database via runtime with no
issues?
3. Are there any known issues or drawbacks to using runtime (faults,
erorrs, etc)?

My employer is not worried about spending the money, he only wants a
seamless upgrade to Access 2007 with no change in functionality by
the users.

Thanks!

What hasn't yet been pointed out is that an app has to be built with the
notion that it might be used in the runtime. The runtime is for fully
polished apps that have replaced all user interface devices with custom
ones.

There is no access to the navigation pane in the runtime. There is no
access to the built in ribbons and shortcut menus. How many of your apps
(right now) would be usable in such a scenario? For example, if you don't
have a start up form and custom ribbons defined then the user of the runtime
will see nothing but a blank window with no mechanisms for getting to
anything.

 

[Tony Toews [MVP]]

What it does is compare the fe version number in a local time
with the current version number in a be table.

Not quite. I check the FE file date and time on the server with the
date and time of the file on the local PC at the time the FE was last
copied down. The local FE date and time can change as form filters,
query plans and so forth are updated.

If the fe is out of date, it launches the updater and quits.

The user launches the Auto FE Updater. If there is nothing to update,
or once it's finished copying down the new FE, creating shortcuts and
so froth then the Auto FE Updater launches the FE MDB/MDE/ACCDB/ACCDE

The updater then renames the fe on the user's computer

I just copy down the new FE over top the local FE.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Klatuu]

Oops!
Sorry, Tony. Turns out it is not yours I am using, but I still have the
link to yours saved.
The one I described is one by Datafast Consulting. Found their web site,
but the utility doesn't show up there. Can't remember where I got it, but it
does perform as I described.

 

[a a r o n . k e m p f]

Tony;

keep your tables and queries where they belong-- on a database server-

Take your wares elsewhere; try to sell them to some poor african
children, why don't you?

This is a non-commercial group. Stop selling your shit on the
newsgroups. (oh, i noticed you have a google ad-- stop advertising on
the newsgroups, that is against the TNC)

-Aaron