zelarra821
Registered User.
- Local time
- Today, 15:22
- Joined
- Jan 14, 2019
- Messages
- 840
Good morning.
I want to somehow protect the databases I make for the people who ask me for them.
I had programmed for several years a form that I have called Configuration, so that the user could customize his application.
In the last update I've made to this form, I've added two security buttons:
- One to access the Administration Panel, protected by a password that only I know. It is a FormUser where the code of the hard disk manufacturer and a username are added to a Users table. It also allows you to delete users. This code is reviewed when entering the database, and if it does not exist, a MsgBox of information to the user and access to the Administration Panel, protected, jumps.
- And one last button to enable the Shift key, also protected by a password that only I know.
The next step I would like to take is to protect the Visual Basic code.
As I have read, setting a password to the VBA project is easily removable. The one I have found most feasible is to generate an .accde file.
Therefore, I ask you my doubts about using an .accde file:
1. Can it be unprotected somehow?
2. Can you export the objects (tables, queries, forms and modules) from that type of file?
3. To update the database, I previously deleted all queries, forms, macros, modules, and class modules from the user's file, and imported them from the original file I had that I had updated. With the .accde file, you would have to import the tables and queries. Are there any drawbacks that you are missing that are important?
4. Are these three layers of security enough?
I assume that I will always have the original version and the user accesses the .accde file.
I hope your answer.
All the best.
I want to somehow protect the databases I make for the people who ask me for them.
I had programmed for several years a form that I have called Configuration, so that the user could customize his application.
In the last update I've made to this form, I've added two security buttons:
- One to access the Administration Panel, protected by a password that only I know. It is a FormUser where the code of the hard disk manufacturer and a username are added to a Users table. It also allows you to delete users. This code is reviewed when entering the database, and if it does not exist, a MsgBox of information to the user and access to the Administration Panel, protected, jumps.
- And one last button to enable the Shift key, also protected by a password that only I know.
The next step I would like to take is to protect the Visual Basic code.
As I have read, setting a password to the VBA project is easily removable. The one I have found most feasible is to generate an .accde file.
Therefore, I ask you my doubts about using an .accde file:
1. Can it be unprotected somehow?
2. Can you export the objects (tables, queries, forms and modules) from that type of file?
3. To update the database, I previously deleted all queries, forms, macros, modules, and class modules from the user's file, and imported them from the original file I had that I had updated. With the .accde file, you would have to import the tables and queries. Are there any drawbacks that you are missing that are important?
4. Are these three layers of security enough?
I assume that I will always have the original version and the user accesses the .accde file.
I hope your answer.
All the best.