Yesterday I came accross an interesting Access installation where one
PC had full rights over the Access application (shiftkey to bypass
startup options etc.), but other PCs had Access installed so that it
was not possible to bypass the startup options when opening the same
application. The manager said that the other PC's did not have a
'full' installation of Access, but did not know how these reduced
functionality versions of Access had been installed.

Can anyone explain this, because I there are many applications where
this behaviour would be useful. The Application on the reduced
functionality installation ran normally. The application does not have
AllowBypassKey disabled.

I guess this must be something that can be done when installing Access
on a PC.

Any ideas?

On Wed, 21 Jan 2009 03:18:27 -0800, iano wrote:

They have only the Access runtime installed. It is the same program but
with lots of registry settings that strip out design capability.

In older versions the developer had to purchase additional software that
gave him the ability and license to create runtime installation packages
and distribute them (the runtime is free for those actually using it).
Starting with Access 2007 the runtime is now free for the developer too.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Ages ago I wrote a Db which sort of stopped other Dbs being interfered with.
You could limit the number of users and set the Db properties such as allow
bypass key, show database windows allow toolbars or menus.

If it's any use...

Phil
"Rick Brandt" <rickbrandt2 (AT) hotmail (DOT) com> wrote

On Jan 21, 12:21*pm, Rick Brandt <rickbran... (AT) hotmail (DOT) com> wrote:
Rick,

That could be the explanation, but although I didn't do the original
instalation which was a single application, I have split it, renamed
the two databases generated, modified the application, and changed
where it runs from. I didn't make it into a runtime and I know the
customer doesn't have the skills to do that. I can still see the VBA
code in the application from the PC with the full version of Access
which I don't think I would be able to if it was a runtime version.

I still wonder if thre isn't some Access installation option that can
produce this behaviour

Ian

On Thu, 22 Jan 2009 00:57:45 -0800, iano wrote:
You misunderstand how the runtime works. It does not alter the Access
file in any way at all. All it does is give you a means to install a
crippled version of Access on a persons PC without having to pay for a
full-blown copy. While the user of the runtime could not access the VBA
code, anyone with a licensed copy can still do so.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

On 22 Jan, 12:22, Rick Brandt <rickbran... (AT) hotmail (DOT) com> wrote:
Thanks Rick - all is now clear!

Ian