I have a question about security. I have a database. I want all users to have access to edit or delete data via the forms. What I want to prevent is the user just holding shift and editing the tables directly. I really don't want the users to have to log in or use a password, they already have to log on to a secure network. I was wondering if there is a way to just prevent, or password protect, opening a table directly. I still want them to be able to edint table data, I just want to make sure they go through the form to do it. Thanks for your time.
I've written a database for a handful of users in my office, split it and compiled the mde, which they are using fine with no problems *touches wood* so far. This is the first time I've compiled a database into an mde, and I've just noticed that if you hold down Shift when opening the mde, it opens up the database window, showing the forms, queries, reports and macros. The tables are shown as linked, and you can't get into Design view on the Forms and Reports. I doubt that any of my users are savvy enough to have figured this out, but even so, I was wondering what would happen if someone got in and started changing things?
I am just about to set up user level security for my database. Before I do, how do I disable the holding the shift key thing when opening a database to get into the database window?
I want to make it so the users can't see the database window or access the backend data. As I will need to give permissions to use most of the tables, how is this done?
I need to disable the [Shift] key so that when the users open my MS Access database, they cannot by pass the open form and display the database window.
We had code that worked correctly with an MS Access 2000 MDB, and even works with an MS Access 2003 ADP, but the same code is ignored by MS Access 2003 MDB.
We add Module named "DisableByPassKey", here is the code...
Public Function SetProperties(strPropName As String, varPropType As Variant, varPropValue As Variant) As Integer On Error GoTo Err_SetProperties
Dim prps As AccessObjectProperties Dim prp As AccessObjectProperty Dim isPresent As Boolean
Set prps = Application.CurrentProject.Properties For Each prp In prps If (StrComp(prp.Name, strPropName, vbTextCompare) = 0) Then isPresent = True Exit For End If Next
If (isPresent) Then prps(strPropName).Value = varPropValue Else prps.Add strPropName, varPropValue End If
Exit_SetProperties: Exit Function
Err_SetProperties: If Err = 3270 Then 'Property not found Properties.Append prp Resume Next Else SetProperties = False MsgBox "Runtime Error # " & Err.Number & vbCrLf & vbLf & Err.Description Resume Exit_SetProperties End If
End Function
The code does not cause an error, it just seems to do nothing. When I set the [Shift] key to "disabled", then re-open the database, the [Shift] key works once again.
I've a form "data-order" and a button which opens a new form "specific data" passing a value with openargs. I just want to insert data in the second form, minimize it clicking on the "hide" button, insert other data in the first form (eventually re-open the second form to modify the specific data) and save all in their tables clicking the "save" button of the first form. Is it possible to hide the second form without losing the inserted data (to re-view and modify it - if necessary) going back to the first form? Thanks
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??
Just wondering if anyone as delt with creating shift calendars(rota). I had an idea to create a calendar simular looking to the outlook design, but wondered if there were any other ideas out there.
To give you info, I want to create a rota so each shift can see what days they are working. There are 5 shift groups and they all work for 6 days before having 4 rest days. In the 6 days they work, the staff work 2 mornings, 2 Afternoons and 2 night shifts. In effect its like a 10 day week instead of (a normal) 7 day week. Of course there will be holidays, sick's and overtime so the rota needs to be flexible to change each persons shift pattern.
I've seen many calendar programs on the forum, but been unsure how these forms work and so wouldn't know where to start for me to adapt them to my needs.
Believe it or not, we just upgraded from Access 2000 to 2003. In Access 2000, I have my dbs set up so that you must hold the shift key down while opening the db in order to see the database window. In 2003, holding down the shift key isn't working. Is there another way to get the database window open (or am I doing something terribly wrong)?
Question. Our db is protected, in other words, when an user opens the db, no possibility to open any menu is availiable. However, if the user is smart (some are :D) then opening the db with the [SHIFT]-key held down the db opens and those users can edit the tables etc.
It would be just enough for our situation to have the possibility to set a password to the [SHIFT]-key when opening the db.
Is it possible? and if it is, please explain to me how
Hello,I am attempting to create a database for a charity organisation, the database will hold information about there volunteers, roles, languages, building, and shifts.One of the main problems I have at the moment is how would I cater for the shifts. Open Sunday - Monday 6 Shifts at present different days are open for different shiftsAny help pointers greatly appriciated.
Ok, I'm new the access database security. I want to disable the shift key as soon as the database is opened to prevent users from getting to my data. I do have userlevel security in place with modal forms. This is my final step...I hope.
Is there any code or sample database that I may download? Thank you for your advice.
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?
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.
I'm making a dispatch call database that will be sorted at the end of the month based on call types and which shift that call was originated on. Our shifts are 6a-2p, 2p-10p, 10p-6a.
I am figuring that the time would be converted to minutes and then the display would be figured based on which times the minutes occured between. IE: the call origintaed at 0100hrs = 60 minutes. It would figure that 60minutes translates to "Night Shift".
How would I convert time into minutes and how would the if/then be established?
I need a module but haven't got the foggiest on where to start. I have a query that works out whether a staff member has done a sleep in based on their clocking out time (TIME OUT). I also have a column for DAY IN which it stores the day they logged in and HOUSE which indicates which house they clocked in at. What I want to do is determine whether each 'sleep in' is a weekday or weekend shift and at which house. We have different rates of pay based on the houses and whether it is weekend or not.
I have a DB with an AutoExec macro. I created the DB from scratch. When I open the DB from Windows Explorer with the shift key held down the AutoExec macro still runs. If I have people on other computers open the same way it doesn't run. If I open Access first then hold the shift key down it doesn't run. I couldn't find any references to a shift key issue like this. I'm looking for an answer as to why there would be a difference on my PC between opening in WE or directly in Access.
Hi, in some application I have made using a switchboard after starting up, I saw that when the user holds the shift button, this switchboard does not show up automatically. How can i fix it that the user cannot interfere holding this button?
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 have a couple of databases set up with shift key bypass and DB window hide and a couple of menu bar commands hidden (All code taken from this great forum :) ). Recently my company decided to upgrade Access 2000 to Access 2007 and they have given me a test environment and a time frame to convert / test all my applications. I found this concept of ribbon and office links very different and shocking. Is there a way of hidding somethings that you can do with the office links (like compact and repair) and a way of hiding some clusters in the ribbon (like export and import data, have a dtaasheet view of any form? etc) Any help or link along these lines would be helpful.. Thanks, Priya
I wonder if someone could point me in the right direction with this one....
I need to be able to check at any time which person is working a shift on a specific day, and whether they are working a day or night shift. In effect I have 4 engineers, who work on shifts A B C & D. All the engineers work a 4 on, 4 off shift pattern, so for example if engineer A is working day shift, engineer B will be working nightshift, C & D will be on rest days. The pattern rotates every 4 days, so in the case of engineer A:
1st - days 2nd - days 3rd - days 4th - days 5th - rest 6th - rest 7th - rest 8th - rest 9th - nights 10th - nights 11th - nights 12th - nights 13th - rest 14th - rest 15th - rest 16th - rest ...................and so on.
I need to be able to pull up a form that tells me which engineer is working which shift on a selected date -I hope I've explained myself properly. Can this be calculated 'on the fly' using VBA & a reference table or lookup? I'd prefer to do this by programming if possible.
I have a daily file to import. If I hard code the entire file name my code works. My problem is getting around the daily name change of the file.The owner has an automated process that creates the file so the name every day is slightly different due to the timestamp. Here's an example
Today's file is "mydailyfile_20140317_1035.xls" Tomorrow will be "mydailyfile_20140318_1033.xls"
I can account for date using "sFileDate = Format(Now(), "yyyymmdd")".The hour/minutes is never the same.is there a wildcard solution??
I am collecting data every hour on the hour and I would like to group this data according to Shift (A, B and C) by Date. The only problem I am having is- how can I keep the overnight shift together as one date? 10pm - 6am
I was able to do a simple query where I was able to assign an A, B, or C depending on the field with the Short Time format using nested IIF statements. From there I was able to group by shift (A, B, or C) per date. However the C Shift is split up.
Example. Can Sunday October 5th 10pm to Monday October 6th 6am be grouped as one date.
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
