Hello!

We need to implement a user-level database security. However, we need to use
two files of type .MDW as follows:

1) Closed Security - To avoid linking tables between databases,
import/export of objects and so on - Default one. This will be only valid
when opening Microsoft Access Application without the Database Application.
2) Open Security - To allow users to open the existing Database Application
without using the user-level security because we already have security
implemented in the database Application.

Database Application = Our Application
Microsoft Access Application = MSAccess.exe

Does anyone know how I could do that?


Thanks in advance



Sandro

On Mon, 22 Dec 2008 05:30:01 -0800, Sandro
<(E-Mail Removed)> wrote:

Provide the user with a shortcut, that includes the /wrkgrp switch to
link to the appropriate MDW.

-Tom.
Microsoft Access MVP


>Hello!
>
>We need to implement a user-level database security. However, we need to use
>two files of type .MDW as follows:
>
>1) Closed Security - To avoid linking tables between databases,
>import/export of objects and so on - Default one. This will be only valid
>when opening Microsoft Access Application without the Database Application.
>2) Open Security - To allow users to open the existing Database Application
>without using the user-level security because we already have security
>implemented in the database Application.
>
>Database Application = Our Application
>Microsoft Access Application = MSAccess.exe
>
>Does anyone know how I could do that?
>
>
>Thanks in advance
>
>
>
>Sandro

Grant permissions to the Users group for every object that you want to
be "open". Any user of any Access installation will be able to use
those objects. Deny permissions to the Users group for those objects
you want to be "closed". Use a customized MDW to grant permissions to
the closed objects to the appropriate user groups in the customized
MDW. Provide a shortcut to open the database file using the customized
MDW.



On Mon, 22 Dec 2008 05:30:01 -0800, Sandro
<(E-Mail Removed)> wrote:

>Hello!
>
>We need to implement a user-level database security. However, we need to use
>two files of type .MDW as follows:
>
>1) Closed Security - To avoid linking tables between databases,
>import/export of objects and so on - Default one. This will be only valid
>when opening Microsoft Access Application without the Database Application.
>2) Open Security - To allow users to open the existing Database Application
>without using the user-level security because we already have security
>implemented in the database Application.
>
>Database Application = Our Application
>Microsoft Access Application = MSAccess.exe
>
>Does anyone know how I could do that?
>
>
>Thanks in advance
>
>
>
>Sandro

--
(E-Mail Removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

Dear All,


Thank you all for the information provided. I will try to keep the
information here as updated as possible, but for now, the problems seems to
be solved.



--
Sandro


"Sandro" wrote:

> Hello!
>
> We need to implement a user-level database security. However, we need to use
> two files of type .MDW as follows:
>
> 1) Closed Security - To avoid linking tables between databases,
> import/export of objects and so on - Default one. This will be only valid
> when opening Microsoft Access Application without the Database Application.
> 2) Open Security - To allow users to open the existing Database Application
> without using the user-level security because we already have security
> implemented in the database Application.
>
> Database Application = Our Application
> Microsoft Access Application = MSAccess.exe
>
> Does anyone know how I could do that?
>
>
> Thanks in advance
>
>
>
> Sandro