|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
bypass shift keyIs there a simple way to disable the use of the shift key so that individuals
cannot get access to tables and other fuctions in a database. I have my database opening to a form but I don't want anyone to have access to the information in the background. Also, I myself would still want to have acces to these table, etc. any Ideas You can use Albert Kallal's utility (of course your users could also use it to re-enable the shiftkey, if they know about it).
Look for 'By Pass Shift Key Code' at http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html -- Joan Wild Microsoft Access MVP Show quote "sandrao" <sand***@discussions.microsoft.com> wrote in message news:0433E918-51D1-4089-ABC4-DD97C331ABDD@microsoft.com... > Is there a simple way to disable the use of the shift key so that individuals > cannot get access to tables and other fuctions in a database. I have my > database opening to a form but I don't want anyone to have access to the > information in the background. Also, I myself would still want to have acces > to these table, etc. > > any Ideas "Joan Wild" <jwild@nospamtyenet.com> wrote in message You can use Albert Kallal's utility (of course your users could also use it news:OvlX2qTJIHA.1184@TK2MSFTNGP04.phx.gbl... to re-enable the shiftkey, if they know about it). You can minimise those chances by using code to detect that the admins group is being used: Sub SetBypassProperty() 'Tries to set the AllowBypassKey property and creates it if it fails to find it. 'Calls libChangePropertyDdl Const DB_Boolean As Long = 1 ChangePropertyDdl "AllowBypassKey", DB_Boolean, False End Sub Function ChangePropertyDdl(stPropName As String, PropType As DAO.DataTypeEnum, vPropVal As Variant) As Boolean ' Uses the DDL argument to create a property that only Admins can change. ' Current CreateProperty listing in Access help is flawed in that ' anyone who can open the db can reset properties, such as AllowBypassKey On Error GoTo ChangePropertyDdl_Err Dim db As DAO.Database Dim prp As DAO.Property Const conPropNotFoundError = 3270 Set db = CurrentDb ' Assuming the current property was created without ' using the DDL argument. Delete it so we can ' recreate it properly db.Properties.Delete stPropName Set prp = db.CreateProperty(stPropName, PropType, vPropVal, True) db.Properties.Append prp ' If we made it this far, it worked! ChangePropertyDdl = True ChangePropertyDdl_Exit: Set prp = Nothing Set db = Nothing Exit Function ChangePropertyDdl_Err: If Err.Number = conPropNotFoundError Then ' We can ignore when the prop does not exist Resume Next End If Resume ChangePropertyDdl_Exit End Function Keith. www.keithwilby.com The OP never mentioned whether the mdb was secured, so I assumed it wasn't - it won't make a difference in an unsecured mdb.
-- Joan Wild Microsoft Access MVP Show quote "Keith Wilby" <h***@there.com> wrote in message news:47386e01$1_1@glkas0286.greenlnk.net... > "Joan Wild" <jwild@nospamtyenet.com> wrote in message > news:OvlX2qTJIHA.1184@TK2MSFTNGP04.phx.gbl... > You can use Albert Kallal's utility (of course your users could also use it > to re-enable the shiftkey, if they know about it). > > You can minimise those chances by using code to detect that the admins group > is being used: > > Sub SetBypassProperty() > > 'Tries to set the AllowBypassKey property and creates it if it fails to find > it. > 'Calls libChangePropertyDdl > > Const DB_Boolean As Long = 1 > ChangePropertyDdl "AllowBypassKey", DB_Boolean, False > End Sub > > Function ChangePropertyDdl(stPropName As String, PropType As > DAO.DataTypeEnum, vPropVal As Variant) As Boolean > > ' Uses the DDL argument to create a property that only Admins can change. > ' Current CreateProperty listing in Access help is flawed in that > ' anyone who can open the db can reset properties, such as AllowBypassKey > > On Error GoTo ChangePropertyDdl_Err > > Dim db As DAO.Database > Dim prp As DAO.Property > > Const conPropNotFoundError = 3270 > > Set db = CurrentDb > ' Assuming the current property was created without > ' using the DDL argument. Delete it so we can > ' recreate it properly > db.Properties.Delete stPropName > Set prp = db.CreateProperty(stPropName, PropType, vPropVal, True) > db.Properties.Append prp > > ' If we made it this far, it worked! > ChangePropertyDdl = True > > ChangePropertyDdl_Exit: > Set prp = Nothing > Set db = Nothing > Exit Function > > ChangePropertyDdl_Err: > If Err.Number = conPropNotFoundError Then > ' We can ignore when the prop does not exist > Resume Next > End If > Resume ChangePropertyDdl_Exit > End Function > > Keith. > www.keithwilby.com > "Joan Wild" <jwild@nospamtyenet.com> wrote in message The OP never mentioned whether the mdb was secured, so I assumed it wasn't - news:%239v6xOWJIHA.3636@TK2MSFTNGP03.phx.gbl... it won't make a difference in an unsecured mdb. Good point Joan. I made a false assumption. Keith. "Keith Wilby" <h***@there.com> wrote in message news:4739570e$1_1@glkas0286.greenlnk.net... Well I may have too, who knows. But Albert's utility covers a secure mdb as well.> "Joan Wild" <jwild@nospamtyenet.com> wrote in message > news:%239v6xOWJIHA.3636@TK2MSFTNGP03.phx.gbl... > The OP never mentioned whether the mdb was secured, so I assumed it wasn't - > it won't make a difference in an unsecured mdb. > > Good point Joan. I made a false assumption. -- Joan Wild Microsoft Access MVP I downloaded the utility from Albert Kallal and it works fine. Just one
other question, If I disable the shiftkey in a data base in my computer and then zip it and pass it on to the individual who will be using it and it is placed in his computer will the disable effect still work? Show quote "Joan Wild" wrote: > You can use Albert Kallal's utility (of course your users could also use it to re-enable the shiftkey, if they know about it). > > Look for 'By Pass Shift Key Code' at http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html > > > -- > Joan Wild > Microsoft Access MVP > "sandrao" <sand***@discussions.microsoft.com> wrote in message news:0433E918-51D1-4089-ABC4-DD97C331ABDD@microsoft.com... > > Is there a simple way to disable the use of the shift key so that individuals > > cannot get access to tables and other fuctions in a database. I have my > > database opening to a form but I don't want anyone to have access to the > > information in the background. Also, I myself would still want to have acces > > to these table, etc. > > > > any Ideas > Yes it will still be disabled.
-- Joan Wild Microsoft Access MVP Show quote "sandrao" <sand***@discussions.microsoft.com> wrote in message news:E26BA5CA-5237-4DD0-A4DE-7D5F9E152745@microsoft.com... >I downloaded the utility from Albert Kallal and it works fine. Just one > other question, If I disable the shiftkey in a data base in my computer and > then zip it and pass it on to the individual who will be using it and it is > placed in his computer will the disable effect still work? > > "Joan Wild" wrote: > >> You can use Albert Kallal's utility (of course your users could also use it to re-enable the shiftkey, if they know about it). >> >> Look for 'By Pass Shift Key Code' at http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html >> >> >> -- >> Joan Wild >> Microsoft Access MVP >> "sandrao" <sand***@discussions.microsoft.com> wrote in message news:0433E918-51D1-4089-ABC4-DD97C331ABDD@microsoft.com... >> > Is there a simple way to disable the use of the shift key so that individuals >> > cannot get access to tables and other fuctions in a database. I have my >> > database opening to a form but I don't want anyone to have access to the >> > information in the background. Also, I myself would still want to have acces >> > to these table, etc. >> > >> > any Ideas >> Thank You
Show quote "Joan Wild" wrote: > Yes it will still be disabled. > > -- > Joan Wild > Microsoft Access MVP > "sandrao" <sand***@discussions.microsoft.com> wrote in message news:E26BA5CA-5237-4DD0-A4DE-7D5F9E152745@microsoft.com... > >I downloaded the utility from Albert Kallal and it works fine. Just one > > other question, If I disable the shiftkey in a data base in my computer and > > then zip it and pass it on to the individual who will be using it and it is > > placed in his computer will the disable effect still work? > > > > "Joan Wild" wrote: > > > >> You can use Albert Kallal's utility (of course your users could also use it to re-enable the shiftkey, if they know about it). > >> > >> Look for 'By Pass Shift Key Code' at http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html > >> > >> > >> -- > >> Joan Wild > >> Microsoft Access MVP > >> "sandrao" <sand***@discussions.microsoft.com> wrote in message news:0433E918-51D1-4089-ABC4-DD97C331ABDD@microsoft.com... > >> > Is there a simple way to disable the use of the shift key so that individuals > >> > cannot get access to tables and other fuctions in a database. I have my > >> > database opening to a form but I don't want anyone to have access to the > >> > information in the background. Also, I myself would still want to have acces > >> > to these table, etc. > >> > > >> > any Ideas > >> > Thank You
Show quote "Joan Wild" wrote: > Yes it will still be disabled. > > -- > Joan Wild > Microsoft Access MVP > "sandrao" <sand***@discussions.microsoft.com> wrote in message news:E26BA5CA-5237-4DD0-A4DE-7D5F9E152745@microsoft.com... > >I downloaded the utility from Albert Kallal and it works fine. Just one > > other question, If I disable the shiftkey in a data base in my computer and > > then zip it and pass it on to the individual who will be using it and it is > > placed in his computer will the disable effect still work? > > > > "Joan Wild" wrote: > > > >> You can use Albert Kallal's utility (of course your users could also use it to re-enable the shiftkey, if they know about it). > >> > >> Look for 'By Pass Shift Key Code' at http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html > >> > >> > >> -- > >> Joan Wild > >> Microsoft Access MVP > >> "sandrao" <sand***@discussions.microsoft.com> wrote in message news:0433E918-51D1-4089-ABC4-DD97C331ABDD@microsoft.com... > >> > Is there a simple way to disable the use of the shift key so that individuals > >> > cannot get access to tables and other fuctions in a database. I have my > >> > database opening to a form but I don't want anyone to have access to the > >> > information in the background. Also, I myself would still want to have acces > >> > to these table, etc. > >> > > >> > any Ideas > >> >  |
|||||||||||||||||||||||
Other interesting topics