Password Protect Autoexec

[MattK23]

Is there a way to password protect the autoexec macro? If not, how would I go about securing that macro? I've noticed that you can import the autoexec macro to a blank database, manipulate the autoexec (i.e. disable shift-key bypass) and export the autoexec back into the database.

Note: the database is already split into FE and BE and both are password protected. The code is already password protected. I thought my system was secure but a friend whom I challenged to break into it was able to get to my code.

He confessed to manipulating the autoexec file so how is a guy supposed to secure his access system now?!!

 

[boblarson]

Make your frontend into an MDE file that way you cannot get to macros.

 

[MattK23]

OK that works for the macros. Now I noticed that I can import all my linked tables from the mde. That's not good. Anyone know a way of securing the tables and maybe even the queries from an mde?

 

[boblarson]

OK that works for the macros. Now I noticed that I can import all my linked tables from the mde. That's not good. Anyone know a way of securing the tables and maybe even the queries from an mde?

If you have to make sure about that you'll need to move to something like using SQL Server or SQL Server Express as a backend.

 

[georgedwilkinson]

Not as secure: you could "hide" the tables. People can still find them if they know what they're doing.

 

[Banana]

Bob and George already has given you useful answers.

I just want to point out that not all problems are meant to be solved with technology. Sometime it's actually better solved by involving the human resource manager in this and thus threatening dismissal of any employees who tamper with company's property and thus costing company's money. Generally speaking, employees usually have an incentive to keep the application running smoothly.

Of course, if you're planning to distribute the application as a commercial program, that's something else.

 

[mikebaldam]

Please Note this is not a secure fix but if your just trying to keep it very simple:

 Dim strInput As String, strMsg As String

strMsg = "Enter the password."
strInput = InputBox(Prompt:=strMsg, Title:="Password", XPos:=2000, YPos:=2000)

If strInput = "APASSWORDHERE" Then
   'Do Whatever
    DoCmd.OpenForm "YOURFORM"
Else
   'Do Whatever
   Exit sub
End If

But if anyone has access to the code they can of course just read the password, so this is not a secure way of doing things.

 

[DCrake]

Convert your AutoExec macro to visual basic and place in a start up module. Then revise your AutoExec macro to run the function in the start up module. Hide the module and the macro. Password protect your code, then make an mde.

In your back end make this password protected then go to your link table manager and relink your tables. It will ask you for the password (once only) it will then refresh the links. You could hide the tables as well (optional).

Like said before if they want to get in they will always find a way. It just takes longer, and in the end they may give up.

David