open accdr file protected with database password

Hi dear

Thanks alot for your notice

1-I wanted only to compare the security of them and my mean was the password that entered by hand that you assume it is only in my mind , so I think your reply is "c"

2- There is a serious problem i n your method that If it does'n solve we can't use of it actually that I hope you solve it  and that problem is :

I don't allow to user , that can use of ribbon or access right click menu abillity and instead of it I built my right click menu specially so when I use of your good method , this right click is disable

How can I resolve this

regard

if I open my protected database with database password by input password with my hand (generally)  or I open it by your method in runtime

which of them has more secureity :

a: with my hand     b: your method    c:  equal

If the database password is not stored anywhere, but remains solely in your head until you enter it in response to a prompt, then I don't think it matters whether the prompt comes directly from Access when the protected database is opend, or from the code that automates the opening of the protected database.  Under those conditions, my answer would be (c).

If, however, you store the password somewhere on your computer, either in the code itself or in some table or file where you can read it when automating the protected database, and so not have to prompt the user at all, then clearly (a) is the correct answer.  Stored data can always be read by anyone who has access to the device on which it resides -- though higher levels of encryption can make that hard enough not to be worth the trouble.

Hi dear

thanks alot

my mean is simple

if I open my protected database with database password by input password with my hand (generally)  or I open it by your method in runtime

which of them has more secureity :

a: with my hand     b: your method    c:  equal

regard

Access has it's power of security , no problem , but my question is :

this way , you give us ,doesn't reduce the power of this security of the MS Access for cracking , does it ?

I'm not sure I understand your question, but I don't see this technique as weakening or bypassing the security of the database password -- you do have to supply the password to open the database.  It just bypasses what in my view is a weakness of the runtime structure, that it requires you to specify a database when opening access, but there is no way to specify the database password on the command line, the way there is for user-level (workgroup) security.

Understand, I don't speak for Microsoft in this matter.  I just tried to find a solution to a practical problem.

Hi dear

thanks alot

Access has it's power of security , no problem , but my question is :

this way , you give us ,doesn't reduce the power of this security of the MS Access for cracking , does it ?

regard