trying to lock people out of using anything but the main menu and its links

[Zetheroth]

This database has been made so that someone with little to know access knowledge could use it hopefully, but I don't want them to be able to change anything because they have been known to break these in the past. so my goal is to lock them out of being able to manually chance what they are on and only able to use the premade buttons to navigateSales Examples.zip

[ranman256]

I use this Lockout app. run it in the same folder as your db,
select db from list,
Lock.

then users cannot use the shift-bypass, nor get to the tables or code.

[Zetheroth]

I'm getting a 3386: Property 'Name' must be set before using this method

[ranman256]

some db's it gives funky errors, but still locks the db. Is this true?

[isladogs]

You should do a number of things including hiding the navigation pane & ribbon, disable shift bypass, save as ACCDE etc
This will significantly improve security though no Access database can ever be 100% secure

Have a look at my article Securing Your Database - A Tutorial. It includes an example app you can use for testing the different methods

[isladogs]

@Ranman256
For info, I just tried your app in 32-bit Access 365 & got a whole series of errors.
On opening, I get this error:



That's an error related to use of your custom ribbon in a different version

I first tried it by adding the OPs database to the dropdown's empty value list and clicked Lock Database which triggered this error repeatedly.



After it appeared 8 times, your app closed without warning.
There was no effect on the selected database

Instead of manually adding items to a value list, having a browse button to select the database would, in my opinion, make it easier for end users

I then placed it in the same folder as you stated and also got error 3386
At this point I gave up. I didn't examine your code other than to report that it didn't compile - extra End If in cmdUnlockDatabase_Click

[Zetheroth]

so... I cant have them use runtime because the users will be on the same computer that I use, I need a way to password lock the functions instead where I can give a password to unlock it, also if needed I have a final version of the document I'm trying to lock them out of. Ideally they only have access to forms, and the forms they have access to are based of the main menu form that it starts on, they also need to see the reports in print mode, but the system has a way to call them they don't need to do it themselves

[CJ_London]

I cant have them use runtime because the users will be on the same computer that I use

it's a fairly weak security measure, although it does add another level, but renaming your file as .accdr simulates a runtime environment. It's weak because users with a bit of knowledge can change it back again.

Ideally they only have access to forms

not sure if it is covered by Colin's link but don't forget to disable right click menus or replace them with your own. Right clicking on the form window bar for example gives you this


Not a problem with runtime since that disables right click menus - and if your users use a .accde they won't be able to get into design view anyway

If your users are using your computer - are they logging in themselves? or using your login? If the former you can keep a development copy (.accdb) in your documents folder or similar (C:\users\your username) that only you can see, and put the production copy in a folder that is shared by everyone

[isladogs]

Yes, I do mention disabling right click context menus in my article

BTW the screenshot above must be from A2010.
I believe the two Pivot items no longer appear as they were deprecated in A2013. Not sure what Menu Details is - a custom item?

[CJ_London]

Correct 2010. Menu details is a temporary option I added. Clicking it tells you all about the selected shortcut- properties and controls. It is dropped when the app is closed

[isladogs]

Correct 2010. Menu details is a temporary option I added. Clicking it tells you all about the selected shortcut- properties and controls. It is dropped when the app is closed

That's an interesting idea.

[CJ_London]

Can show you tomorrow!

[isladogs]

Can show you tomorrow!

I know - that was my way of encouraging you to do so!

[Zetheroth]

Thanks everyone! got the doc from @Ranman256 working, for some reason while access is open I get like a shadow of the document that stays a while after closing. Once that fake copy vanishes I can lock and unlock, there was an extra "end if" in the code, but i cleaned it out. Onto another issue on another post!

[ranman256]

--------------------------