User Protection System...(XP)

  • Thread starter Thread starter ALESSANDRO Baraldi
  • Start date Start date
A

ALESSANDRO Baraldi

Hi.
I'm usually work again on A97, but my new application w'll be run
also on XP version.
I protect it with User System building MyProtection.MDW, for
all Modules, Tables, Forms and Queries...!
On A97 all OK.
On XP i have no the possibility to extend my protection to Modules
and to all CODE.
I try it, but my Code is always visible, some error occur, but i see the
code.

Sure i made a mistake, but if no modifie(form MS) to the protection system
are made
i'm also sure to do it in a right way......!

Any suggestions or any solutions are gratefully received.

Thanks.
@Alex.
 
Access versions after A97 do not use "user level security" to protect
code modules. They use the so-called "VBA (VBE?) password". This is an
extra password, seperate to the database password & user-level
security passwords. It is an "all or nothing" thing. If you enter it,
this protects *all* the modules. If you do not enter it, *none* of the
modules are protected. There is no way to protect some modules but not
other ones. I'm not sure whether these changes were introduced with
A2000, or with A2002.

I thought that if you converted an A97 database to A2000 (A2002?), the
module level security *would be carried through*. Apparently that is
not happening in your case. But even if it did happen, there is still
no way to administer (change) an individual module's permissions from
within A2000 or A2002.

If you want to secure *all* the modules, just add a VBA (VBE?)
password from within A2000 (A2002?).

HTH,
TC
 
TC said:
Access versions after A97 do not use "user level security" to protect
code modules. They use the so-called "VBA (VBE?) password". This is an
extra password, seperate to the database password & user-level
security passwords. It is an "all or nothing" thing. If you enter it,
this protects *all* the modules. If you do not enter it, *none* of the
modules are protected. There is no way to protect some modules but not
other ones. I'm not sure whether these changes were introduced with
A2000, or with A2002.

I thought that if you converted an A97 database to A2000 (A2002?), the
module level security *would be carried through*. Apparently that is
not happening in your case. But even if it did happen, there is still
no way to administer (change) an individual module's permissions from
within A2000 or A2002.

If you want to secure *all* the modules, just add a VBA (VBE?)
password from within A2000 (A2002?).

HTH,
TC
Click to expand...

Thanks for INFO, but i look in Application.VBE properties and i don't
find any reference to a Password.....!

Can you give me an exemple of VBA code to set all protection
around Modules.....?

Thanks again.

@Alex.
 
Back
Top