To set the AllowBypassKey property to False, follow these steps: 1. Start Access.
2. Open an Access database project.
3. In the Database window, point to Macro on the Tools menu, and then click Visual Basic Editor.
4. In the Visual Basic Editor, click Immediate Window on the View menu.
5. Type the following code or paste the following code in the Immediate window, and then press ENTER.CurrentProject.Properties.Add "AllowBypassKey", False
6. Close the Visual Basic Editor, and then close the Access database project.
7. Open the Access database project. Try to bypass the startup options that are set for the Access database project by holding down the SHIFT key while you open the Access database project.
The functionality of the SHIFT key that permits you to bypass the startup option is disabled. Although you hold down the SHIFT key to bypass the startup options, the startup options are executed. You cannot bypass the startup options.
Is there a way to change the shift key and use another key on startup?? Security for me isn't a big issue... but I'd still like to protect things from being tampered with. I don't want to use MS security (I use it on other DBs) but its not really approriate on the one I'm developing. Any ideas??
In Access 2010 I'm setting and unsetting the bypass shift key property - set to true for users and set to false for me, the developer. No problem but what I can't figure out is how do I work out whether it is set or not?
I am able to bypass the shift key so I can disable ribbon and all menus at startup.
But the issue I have is anytime someone makes a copy of the database or it is their first time opening it they get prompted with the security warning:
"Security Warning - some active content has been disabled, click here to enable"
and it gives them complete access to see the back end of the database because while that warning message is popped up ... before they click "enable" they can go do anything in the database including see tables, data, and vba.
Once they click "enable content" that first time the bypass takes effect and the ribbon and all menus disappear, but if they dont click it they can navigate all around the db
I would like to secure my database (ha ha...at least to some extent). Here is the basics... When someone comes into the database I can identify them as they enter by using "Environ("username"), this gives me a unique number for that user ("R54436") (I am on a system called "Citrix" with FE/BE) and from there I would like to: 1.) let them in or not let them in 2.) direct them to particular areas based on who they are 3.) deny access to certain areas all together
I have a table in which I have all users "R" number along with name, user level (1,2 or 3) and the branch office number and can add other info if needed.
I have a form that loads before anything else (invisible) that captures the users "R" number.
I guess I am just not sure how to compare the "R" number that I capture on the invisible form with the "R" numbers in my table. Ultimately once I find a match I would like to populate the invisible form with that users values from the table so I can reference those values throughout their vistit.
How do I secure my database so no one can install it on other computer I know I can make the MDE file, but any one can use it.. is there a way to create a installation setup so it needs a serial o something like that.. if so what do I have to do? I don't want my database to be installed unless I provide the authorization
My program is finally complete, much thanks to everyone here that helped me!
Here's (hopefully) my final issue:
I haven't actually tested this yet to see if it's an actual issue, but I assume it might be. The program i just built needs to be transferred to my client's computer. currently my program consists of three files: PROGRAM.mdb (interface), DATA.mdb (linked tables), PROGRAM.mdw (security file). they are in their own separate folder (C:Program) and play nicely together. i'm concerned because i think that once i zip it up and email it over, when my client unzips it into a folder on his hard drive (named c:program so he doesn't have to re-link them), it might not work because of the .mdw file. if anyone recalls my thread entitled "H E L P ! ! ! !" you see why I'm concerned.
should this just run without a problem, or do i need to have him do all sorts of steps to reassemble the program?
I am kinda new to 2007 and have at the moment a simple database.
I want three things
A: Use the database on a server.
B: Restrict the use to users etc as i used to be a ble to do in Access 97 i think (do i have to make a MDW if so how ?) 9I tried ACCDE but does not seem to do anything)
C: When users use the datavase not see all the normal access editing stuf..
This morning I accidently ran the "User-Level security wizard" on a secure database that we use. I meant to add a member but clicked the wrong thing and followed suite by hitting "Finish" instead of cancel because I wasn't paying attention. Aside from creating a "Security.mdw" file which isn't being used at all, it also somehow managed to lock everyone but the administrator out.
I checked the Users/Groups and Permissions, they are all there and correct, nothing seems to have been changed at all but when anyone tries to log in now they get the following error:"You do not have the necessary permissions to use the '...mdb' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."
I've read some posts with similarish issues that recommended recreating the .mdw file and importing the data over. The file is encrypted so I wasn't able to do that but I did try making a copy and renaming it then changing the path in the Access shortcut to the copy instead. What all files/settings handle this and if the Users/Groups show up correctly in the database, what could be preventing the users from getting in?
I've made an access project (ade) and stored the admin with password in the ade file. When I open a new database I can use the import feature to import all tables with definitions and data from the ade file. All other objects are being locked.
How can i disallow tables from my mde to be imported into another access application?
Normally when I hold down the shift key when opening an Access database it opens in development mode. When I do this on a certain database it does not. It still opens in program mode. If I hit F11 it goes into a sort of development mode but I do not get the ribbon bar at the top etc.
Has something been set on this database to stop it opening in development mode? Can I switch it off?
I was reading the threads related to bypass issues...
Now I know how to disable (or enable) shift key of a database with password using the code provided by ghudson: http://www.access-programmers.co.uk/forums/showthread.php?t=51479&highlight=bypass
In other thread he provided another way to enable or disable the shift key using another method: (developed by Ricky Hicks):
this one can easily disable or enable the shift key of any database... even if that is disable with the password protected method provided by ghudson...
so... my question... is there any method that will ONLY allow enable or disable the key with a password?
On my form the first control which gets focus has a code which cannot contain a null value. It may happen nevertheless that users may need to just close the form without making an entry in this control (listbox).
Is there a way I can add a code to a cmbbutton to skip that forced entry meaning to leave the control null and exit the form? Thank you.
If I hold down the SHIFT-key and click on my access database the database boots up with the startup options! I can't get into my database even if I hold down the SHIFT key!! Help me, please
I've used this parameter back in Access 2.0 where I ask for I put [What location?] as the parameter and users can put 'North' or hit enter to get all locations.
I have split my DB, FE & BE. The BE is located on a network drive and the FE is located on several local network drives for staff to use. Once I created a password for the BE, the main form would not open for the user on the FE. How can I secure the BE so the data can't be opened.
I am finding a way to secure my BE on the server, sooner or later they will find a way to extract information w/o the use of my application and will cause more problems.
I tried to put a PW on the BE but everytime I connect on the BE it prompts me a PW, sorry I am a newbie.
I know that I can startup MS-Access manually and bypass the startup options, including any macro that is set to run automatically, by holding the Shift key down when launching the application. I have:
Code: Public Sub AccessStuff() Dim myaccess As New Access.Application myaccess.OpenCurrentDatabase(" orfs006slsops_repts\_RS DevSOPSOP.MDB") Dim db = myaccess.CurrentDb() End Sub
which works nicely and opens the database just fine. However, this mdb has a startup macro defined in it. I can't hold down the Shift key since I'm doing this from a program. In this case, how can I bypass the startup macro?
I am looking for a way to secure a single DB. I would like to be able to use the DB on other PC, but still have user control.
I have found that when using the MS Access User and Ground way will only secure DB's used on the PC it was set on. If i take the DB to my home PC i am not promted for a Password and i can go mad with information i would like to protect.
Am i doing something wrong when setting the security? :confused:
Hi all. I know Access security has been discussed ad nauseum in these forums and that there is a wealth of information in the archives, nearly all of which I have read often.
And I have a small question.
For years I produced applications which didn't need tight security. However, I tried to stay well informed on the matter.
Security is important in this project. I secured a database properly, as well as I can determine. I then made a copy and deleted all the tables in the one which will be the frontend and linked to the tables in the copy which will be the backend. Only Groups had permissions, individual Users, none. Life was good.
Then I did something, not sure exactly what. The end result is that the frontend seems fine; I cannot open it unless attached via the .mdw I created specifically for this project.
The backend, however, I can open even when attached to the system default .mdw.
Can anyone tell me what I've likely done, and how I might nail down the backend once again?
I have a database which is slowly evolving. Users needed a feature to delete some records without a trail and some with a trail from the form. So I added an apply action field in the subform using which they can delete a record without a trail and if they wanted to keep a trail they could do that too. When user selects "Delete Violations as it was entered in error" the system deletes the record completely which is what everyone wanted.
After six months of use now I am asked to add an audit trail. I managed to do that also. I also looked at Browne's method but my data structure does not match the requirements for that method. I used an alternate method. It works as intended except when a record is completely deleted using the code I mentioned above. Then it goes in the infinite loop. I somehow need to bypass the before update event so that the function to write the audit trail is not called.
I have already used the option in the 'Startup...' menu so that the user only sees the database window with the tables, queries and reports etc. But the user can still press the 'Design button' in the database window. And especially for my queries and reports that would be a problem if they altered things in there by accident.
Is there a way to secure this? Can I hide the queries but still let the user access one table and the reports?
I have tried to search for answers and the runtime command removes everything so that nothing is visible :p
