By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,561 Members | 3,265 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,561 IT Pros & Developers. It's quick & easy.

Securing Microsoft Access Application

P: n/a
Hello, i have a microsoft access application and right now, anyone
knowing how to use microsoft-access can easily go behind the
applicatio, design the forms, delete edit/tables etc... There is
basically no security on the application.

My question is... how do i secure the application, preventing any
access to the "back" or Source (tables,queries,forms,macros...) of the
application? or even preventing getting into the design view of the
form.

A good example of what i want is on this site :
http://www.jamiessoftware.tk
I downloaded the demo, and the software is secure. I cant mess with
any of its source.
I just want my app to have its own custom menus and commands, leaving
access' defualt commands out of it, that way preventing users to go
behind it and mess with the source.
Could anyone please explain any procedures, or any reference sites?
Any help will be highly appreicated
Thanks!
Gil
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Giloosh wrote:
Hello, i have a microsoft access application and right now, anyone
knowing how to use microsoft-access can easily go behind the
applicatio, design the forms, delete edit/tables etc... There is
basically no security on the application.

My question is... how do i secure the application, preventing any
access to the "back" or Source (tables,queries,forms,macros...) of the
application? or even preventing getting into the design view of the
form.

A good example of what i want is on this site :
http://www.jamiessoftware.tk
I downloaded the demo, and the software is secure. I cant mess with
any of its source.
I just want my app to have its own custom menus and commands, leaving
access' defualt commands out of it, that way preventing users to go
behind it and mess with the source.
Could anyone please explain any procedures, or any reference sites?
Any help will be highly appreicated
Thanks!
Gil


Check out the "Microsoft Access Security FAQ" section from this newsgroup's
FAQ, posted 03/05/04 at 18:04.
Nov 12 '05 #2

P: n/a
>
My question is... how do i secure the application, preventing any
access to the "back" or Source (tables,queries,forms,macros...) of the
application? or even preventing getting into the design view of the
form.


All of the features you need to hide the ms-access part and keep users out
can be done via tools->start-up. So, you don't even need to setup security
or anything else.

You should of course give your users a mde file..as that means the code and
forms etc. can not be changed (but, remember to keep your original mdb..as a
mde cannot be reversed back to the original design mdb).

Try downloading and running the 3rd example at:

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

If run it..you will see how all of the access interface is hidden. Now,
exit..and re-run holding down the shift key to "sneak" in:

Take a look at the options that I set in the tools->start-up...
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
pl******************@msn.com
http://www.attcanada.net/~kallal.msn

Nov 12 '05 #3

P: n/a
Use the built in security wizzard. Create Users. Create groups or use
the built in ones. Assign users to group/s. Set appropriate
permissions on objects.

Start the db using the system.mdw file. Access call create the
shorcuts for you.


gi*******@hotmail.com (Giloosh) wrote in message news:<ca**************************@posting.google. com>...
Hello, i have a microsoft access application and right now, anyone
knowing how to use microsoft-access can easily go behind the
applicatio, design the forms, delete edit/tables etc... There is
basically no security on the application.

My question is... how do i secure the application, preventing any
access to the "back" or Source (tables,queries,forms,macros...) of the
application? or even preventing getting into the design view of the
form.

A good example of what i want is on this site :
http://www.jamiessoftware.tk
I downloaded the demo, and the software is secure. I cant mess with
any of its source.
I just want my app to have its own custom menus and commands, leaving
access' defualt commands out of it, that way preventing users to go
behind it and mess with the source.
Could anyone please explain any procedures, or any reference sites?
Any help will be highly appreicated
Thanks!
Gil

Nov 12 '05 #4

P: n/a
Thanks alot guys! the startup feature and MDE method works great,
thats about all i needed.
thanks alot
gil
me****@hotmail.com (Andrew) wrote in message news:<a0**************************@posting.google. com>...
Use the built in security wizzard. Create Users. Create groups or use
the built in ones. Assign users to group/s. Set appropriate
permissions on objects.

Start the db using the system.mdw file. Access call create the
shorcuts for you.


gi*******@hotmail.com (Giloosh) wrote in message news:<ca**************************@posting.google. com>...
Hello, i have a microsoft access application and right now, anyone
knowing how to use microsoft-access can easily go behind the
applicatio, design the forms, delete edit/tables etc... There is
basically no security on the application.

My question is... how do i secure the application, preventing any
access to the "back" or Source (tables,queries,forms,macros...) of the
application? or even preventing getting into the design view of the
form.

A good example of what i want is on this site :
http://www.jamiessoftware.tk
I downloaded the demo, and the software is secure. I cant mess with
any of its source.
I just want my app to have its own custom menus and commands, leaving
access' defualt commands out of it, that way preventing users to go
behind it and mess with the source.
Could anyone please explain any procedures, or any reference sites?
Any help will be highly appreicated
Thanks!
Gil

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.