Coding a module and command button to disable shift override.

[bradp1979]

Can someone more versed in Access '07 please read this: http://www.databasedev.co.uk/disable_shift_bypass.html and essentially hold my hand through the process? I tried, and I couldn't get past copying and pasting the first bit of code into a new module.



Thank you!

[CJ_London]

Before continuing -follow the advice in your link

Note: Always create a backup copy of the database, to test out any areas that may cause problems when working with start-up options or disabling Access features

.

create a button called bDisableBypassKey on a form then copy the 2nd bit of code into that button's click event.

save the form then open it, stand back and click the button

when prompted for a password, per the code type 'TypeYourBypassPasswordHere'

[knarfreppep]

I'm having trouble imagining why one would want a button in an application to disable the Shift key ... if one has one's mouse/finger poised over such a button, one must have already opened the app ... i.e. one has already had an opportunity to hold down Shift to open the app with it's workings laid bare ... so the horse has bolted.

Shouldn't one always publish a serious app as a .mde ... wouldn't it be best to do that and code the Main Switchboard's OnOpen event to disable the Shift key if the app being opened is a .mde? That is, not if the source .mdb is being opened.

If that's how you want to do it, yell out and I'll upload suitable code.

[ItsMe]

I'm having trouble imagining why ...

Creating an executable will get rid of the VBA. The biggest hurdle is keeping the Users from Options and Objects. Bypassing the Shift Key is one, good, step towards protecting your app.

[knarfreppep]

I'll upload code for the Main Switchboard (i.e. default form) just in case.

Note that you must open the .mde at least once before publishing it to your users so this code runs before they get a chance to open it with Shift down.

Private Sub Form_Load()

If CodeDb.Properties("MDE") = "T" Then
mfctByPassKey_Disable
End If

End Sub


Private Function mfctByPassKey_Disable()

On Error GoTo Error_mfctByPassKey_Disable

CodeDb.Properties("AllowByPassKey") = False

Exit_mfctByPassKey_Disable:
Exit Function

Error_mfctByPassKey_Disable:
Select Case Err
Case 3270
CodeDb.Properties.Append CodeDb.CreateProperty("AllowByPassKey", dbBoolean, False)
Resume Next
Case Else
MsgBox Err.Number & " " & Err.Description
End Select
Resume Exit_mfctByPassKey_Disable

End Function

[knarfreppep]

Bypassing the Shift Key is one, good, step towards protecting your app.

I fully agree. But surely not AFTER the app is open?

[knarfreppep]

I don't want to be an Advanced Beginner.

Does anyone know if/how I can become a Novice again please?

[bradp1979]

I'll upload code for the Main Switchboard (i.e. default form) just in case.

As I am a complete and total novice, I find that although I have no problem opening up a module in which to paste this code, I don't know whether to do it on the back end or front end, nor do I know how to make it work once it's saved as something.

[ItsMe]

Here is a working example of what I use. It is not what was in the link. But it is a more simple approach, if you ask me. A form will launch at start up. You can use the shift key to bypass the form launching.

Click the appropriate button to disable or enable the ability to bypass the shift key. There is code behind each of the buttons. The code calls a function. The functions are in a module named modLockMe. Copy the module into the DB that you want to lock.

On a side note, what I do is distribute copies of the FE file to the users. Before I provide a copy of my master copy, I call the function (in the copy) to disable the shift key from the Immediate Window. Then, the copy can be thrown away after use.