Module level security

  • Thread starter Thread starter Peter Wullems
  • Start date Start date
P

Peter Wullems

Try gain with correct "From". Oops!

I am trying to upsize an access application to C# and MS SQL Server 2000.
Data is fine but Access application contains several modules to which I
cannot get access. I can open and design tables, queries, forms, macros etc
but not modules. I have a login at Administrator level but not the dbowner.

What can I do?

any help gratefully received.

cheers
-
 
Having a login as the "db owner" will not necessarily let you access those
modules. Despite a general belief to the contrary, the db owner >is not< one
of the users who >necessarily< has full access to every object in the
database.

Can you view the code of >any< modules?

What version of Access is the db in?

Do you have the workgroup information file that was used to create & secure
the database?

HTH,
TC
 
Can not see any module code at all. There are 8 modules and every time I
attempt to open any of them I get a message saying I don't have permission
to read cls(Name..). It then goes on to say i must have Read Design
permissions for it.

There is a tblzSecurity table that has a ynReadDesign boolean field amongst
others all dealing with different permissions but the module name does not
appear in any record in the ObjectName field or any other for that matter.

I have created new records in this table in an attempt to make it work,
naming the module name as the object name, for the Admins group with all
permissions enabled but nothing happens other than the same old dialogue box
as above.

Can see forms, queries, tables etc and all their code. Just not code in
modules.

I do have the Workgroup information file. And a user login that has admin
rights.

Access version 2000 file format.

cheers, Peter
 
Further progress:

I have been able to create a new WorkGroup Information File with myself
being given every permission under the sun, created a new shortcut that uses
the new .mdw file and can open the database logging in as me.

However the problem with inability to open modules persists. The outcome is
identical to the previous login that I had via the old mdw file.

I can only guess that maybe the protection is in custom code.

Any thoughts??

cheers, Peter
 
If you can see some code behind forms, the db is not in MDE format, so the
module sourcecode is still there.

If you have the workgroup file >>> which was used to create & secure that
database <<<, you should be able to regain access to the module sourcecode,
as follows.

1. Start the database using a shortcut of the following format - all on one
line:
"full path to MSACCESS.EXE"
"full path to MDB file"
/wrkgrp "full path to MDW file"

2. Log-on as a member of the Admins group.

3. Use the Tools:Security interface to grant all necessary permissions to
each module (if those permissions are not already there).

In the step 1. shortcut, you must reference the workgroup file >>> which was
used to create & secure that database <<<. Only the Admins group of that
specific workgroup file, will be able to do what you want. The Admins groups
of >other< workgroup files, will probably not be able to do what you want.

You mention a user login that has "admin rights". IMO, the term "admin
rights" is not particularly well-defined. The login that you really need,
is, "a member of the Admins group of the workgroup file which was used to
create & secure the database".

HTH,
TC
 
Thanks

I was subsequently given the password for the dbowner who is a member of the
Admins group and lo and behold, it all opened up.

Thanks for your help.

cheers

Peter
 
Back
Top