access xp runtime -- view tables in design view?

[sea]

If a runtime installation of Access is created and installed on a
client machine that has a full verion of access, will it still be
possible to view the tables and queries in design view but not the
forms? Thank you very much, Sue

[Steve Jorgensen]

Access and the Access Runtime are each executable files that can open Acces
databases. Installing the Access Runtime on a machine does nothing more than
put the MS Access runtime on the machine. If the full Access was there
before, it is still there afterward and functions as it always did.

If you distribute your Access application with the Access Runtime, that
doesn't have any affect on what happens if the user opens the database using
full Access instead.

If you want to actually protect your Access project, you must use Access
security or create an MDE. An MDE will work much as you describe. The
designs of forms, reports, and code are not available, but the designs of
tables and queries are. You can lock those down as well by using Access
security if you need to.

On 28 Oct 2004 22:43:15 -0700, se*****@hotmail.com (sea) wrote:

If a runtime installation of Access is created and installed on a
client machine that has a full verion of access, will it still be
possible to view the tables and queries in design view but not the
forms? Thank you very much, Sue

[Albert D. Kallal]

"sea" <se*****@hotmail.com> wrote in message
news:f8*************************@posting.google.co m...

If a runtime installation of Access is created and installed on a
client machine that has a full verion of access, will it still be
possible to view the tables and queries in design view but not the
forms? Thank you very much, Sue

Yes, the user would be able to do this. In fact, if you distribute a mdb,
they would also be able to change forms if they have the full version of
ms-access already installed (this assumes you are using a mdb).

However, as a general rule, by the time a budding developer gets around to
using the runtime system, you likely should have provided your own interface
that keeps users "out" of the ms-access part anyway. You can hide all of the
tables etc from your users, and you should do this BEFORE you get around to
using the runtime. In other words, the runtime don't provide any protections
here..but it is quite easy to provide your own UI here, and keep this stuff
away from your general users.

When you get so far as the runtime system, then you should start building
some menus for ms-access. I have thoughts and some nice screen shots of some
ms-access menus here..and this reading will give you some ideas:

http://www.attcanada.net/~kallal.msn...erFriendly.htm

Also, if you want to see a simple application that hides all of the
ms-access stuff, but takes no special code, or even security settings, try
downloading and running the 3rd example here:

http://www.attcanada.net/~kallal.msn...s/DownLoad.htm

The above hides all of ms-access. If you created the above example as a mde,
and disabled the shift key by-pass, you would have something that keeps
people out of the tables and queries. I have a utility here that lets you
remove the shift key by-pass:

http://www.attcanada.net/~kallal.msn.../msaccess.html
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.attcanada.net/~kallal.msn

[sea]

Thank you so very much for the detailed information -- this really helps!
"Albert D. Kallal" <Pl*******************@msn.com> wrote in message news:<DUlgd.53327$Pl.53119@pd7tw1no>...

"sea" <se*****@hotmail.com> wrote in message
news:f8*************************@posting.google.co m...

If a runtime installation of Access is created and installed on a
client machine that has a full verion of access, will it still be
possible to view the tables and queries in design view but not the
forms? Thank you very much, Sue

Yes, the user would be able to do this. In fact, if you distribute a mdb,
they would also be able to change forms if they have the full version of
ms-access already installed (this assumes you are using a mdb).

However, as a general rule, by the time a budding developer gets around to
using the runtime system, you likely should have provided your own interface
that keeps users "out" of the ms-access part anyway. You can hide all of the
tables etc from your users, and you should do this BEFORE you get around to
using the runtime. In other words, the runtime don't provide any protections
here..but it is quite easy to provide your own UI here, and keep this stuff
away from your general users.

When you get so far as the runtime system, then you should start building
some menus for ms-access. I have thoughts and some nice screen shots of some
ms-access menus here..and this reading will give you some ideas:

http://www.attcanada.net/~kallal.msn...erFriendly.htm

Also, if you want to see a simple application that hides all of the
ms-access stuff, but takes no special code, or even security settings, try
downloading and running the 3rd example here:

http://www.attcanada.net/~kallal.msn...s/DownLoad.htm

The above hides all of ms-access. If you created the above example as a mde,
and disabled the shift key by-pass, you would have something that keeps
people out of the tables and queries. I have a utility here that lets you
remove the shift key by-pass:

http://www.attcanada.net/~kallal.msn.../msaccess.html