Access Runtime [with a twist]

[Mell]

Say I have office 2003 professional on my desktop pc @ home, and I want to
deploy a few small access applications w/ runtime [Visio Studio Tools for The
Microsoft Office System]. Am I to understand that when this application is
deployed onto another computer w/ runtime we have to build toolbars, etc for
them to do daily operations on the db? Also, say if I want one of the users
to have all rights to the db window/objects, anotherwards, I just give them a
starting point and they can update it in any way they like. The main user
will have the [bypasskey - code (they can choose and i will insert code) and
as for the other users just like any other application they cannot get to the
design mode because the shift key will be disabled?
Is this still possible to do this when I deploy the application w/ runtime? I
want the transfermation to be as if it was done there and one person usually
maintains anyway. Please advise.
(e-mail address removed) - anyone is more than welcome to help me out on this
subject. NO SPAM......

 

[George Nicholson]

Am I to understand that when this application is

deployed onto another computer w/ runtime we have to build toolbars, etc
for
them to do daily operations on the db?

That's correct. And if you don't have good error handling in place, you
should.

...the other users ...cannot get to the
design mode because the shift key will be disabled?

Not quite. Any users who will be making design changes will require the full
Retail version of Access. Design views are simply not available to Runtime
users, no matter what kind of permissions you grant them and regardless of
the bypass key status. (Runtime = can be used to run it. Period.)

You might want to look at the article:
http://msdn.microsoft.com/library/d.../odecore/html/dehowtargetingaccessruntime.asp
Targeting the Access Run-Time (Access 2000)
Specifically the section :
"Differences Between Full Microsoft Access and the Run-Time Environment",

also (somewhat redundant, but adds a bit of detail to the above):
http://support.microsoft.com/default.aspx?scid=kb;en-us;208730
ACC2000: Differences Between Retail and Run-Time Microsoft Access

While both of these address Acc2000, the principles haven't changed AFAIK.

HTH,
--
George Nicholson

Remove 'Junk' from return address.

Say I have office 2003 professional on my desktop pc @ home, and I want to
deploy a few small access applications w/ runtime [Visio Studio Tools for
The
Microsoft Office System]. Am I to understand that when this application is
deployed onto another computer w/ runtime we have to build toolbars, etc
for
them to do daily operations on the db? Also, say if I want one of the
users
to have all rights to the db window/objects, anotherwards, I just give
them a
starting point and they can update it in any way they like. The main user
will have the [bypasskey - code (they can choose and i will insert code)
and
as for the other users just like any other application they cannot get to
the
design mode because the shift key will be disabled?
Is this still possible to do this when I deploy the application w/
runtime? I
want the transfermation to be as if it was done there and one person
usually
maintains anyway. Please advise.
(e-mail address removed) - anyone is more than welcome to help me out on this
subject. NO SPAM......