Permissions on Modules

  • Thread starter Thread starter Gary D.
  • Start date Start date
G

Gary D.

I have converted several database mdb files from 97 to 2003.

In 97 mdb files I could use the security dialogs to set read permissions for
stand-alone VBA modules, but I cannot find any method for changing security
permissions for modules in 2003, which is preventing me from importing modules
from one mdb to another under different owners.

Can somebody please explain how this can be achieved?

Thanks.
 
Gary said:
I have converted several database mdb files from 97 to 2003.

In 97 mdb files I could use the security dialogs to set read
permissions for stand-alone VBA modules,
Click to expand...

Why would you need to do this?
but I cannot find any method
for changing security permissions for modules in 2003, which is
preventing me from importing modules from one mdb to another under
different owners.
Click to expand...

I would return to the 97 version and grant full permissions on the modules.
Then you can import them.
 
Why would you need to do this?
Click to expand...

I did it because selected modules contain soft encryption coding (nothing
exceptional, pretty simple stuff really) and I wanted to retrict access to the
code by non-secure users.
 
Remember that a fundamental requirement of modern encryption is that
the encryption & decryption algorithms are publically available for all
to see. The secrecy should lie in the key, the whole key, and nothing
but the key.

For example, the current & previous US data encryption standards (AES
and DES respectively) are publically documented (in exhaustive detail),
and there are unlocked implementations of them in various languages
including VB(A) all over the web.

HTH,
TC
 
Back
Top