How to enforce security on hiddent objects?

M

Me

I have hidden all tables, queries, macros and modules.
I would like to setup some security so that only an admin
can access all these. How can I achieve this?

Note that I am using the sql server security, I don't have
any access security.

Thank you,
-Me
 
D

Dirk Goldgar

Klatuu said:
Either use Access User Level security or distribute only an mde
Click to expand...

Note that distributing an MDE won't protect tables, queries, and macros;
only forms, reports, modules, and (I think) DAPs.
 
M

Me

Klatuu,

I am unable to create and mde file and since I am using linked tables and I
have implemented the column level security in sql server and other reasons I
am using sql security.

Is there another way to address this?

Thanks for your time,
-Me
 
R

Rick Brandt

Me said:
Klatuu,

I am unable to create and mde file and since I am using linked tables
and I have implemented the column level security in sql server and
other reasons I am using sql security.

Is there another way to address this?
Click to expand...

If you are using SQL Server security then what harm is there in letting
people see the links? They will only be able to do whatever your SQL Server
security allows them to.
 
M

Me

Rick,

Here is an example, people have read permissions on a table.
But some data in this same table should be hidden from them.
This check is being done using the role, etc.
It is working fine when using forms, etc.
But if they can open up the linked table, then they will be able to view the
secured data.

I hope this answers your question,

Thank you very much,
-Me
 
M

Me

Well Dirk, as far as my knowledge goes, the very purpose of having MDE is
to just execute the stuff, it shouldn't show tables, etc. I will be
surprised if it did so.

You have a point, I will research it more. But can you tell me why the MDE
may be greyed out on my Access database? If I can create an MDE, I think I
will be fine.

Thanks much,
-Me
 
R

Rick Brandt

Me said:
Well Dirk, as far as my knowledge goes, the very purpose of having
MDE is to just execute the stuff, it shouldn't show tables, etc. I
will be surprised if it did so.
Click to expand...

An MDE does absolutely nothing to protect (or hide) tables or queries.
You have a point, I will research it more. But can you tell me why
the MDE may be greyed out on my Access database? If I can create an
MDE, I think I will be fine.
Click to expand...

If you are using Access 2002 or 2003 then the default file format is 2000,
but you can only make an MDE if you first convert to the 2002/2003 format.
 
D

Dirk Goldgar

Me said:
Well Dirk, as far as my knowledge goes, the very purpose of having
MDE is to just execute the stuff, it shouldn't show tables, etc. I
will be surprised if it did so.
Click to expand...

I assure you that what I said is true. The purpose of the MDE is to
protect your code and form/report designs from copying or tampering. An
MDE will not protect your tables and queries from inspection and
modification. For that you need user-level security.
You have a point, I will research it more. But can you tell me why
the MDE may be greyed out on my Access database? If I can create an
MDE, I think I will be fine.
Click to expand...

First, the database must be in the native format for the Access version
you're using. So if you're using Access 2002 or 2003, your database
must be in the Access 2002-2003 file format, not the Access 2000 format.

Second, the database must be able to be compiled successfully. I'm not
completely sure that your "Make MDE" option will be greyed out if there
are compiler errors, but you won't be able to make an MDE unless the
database can be compiled.
 
Top