Access 97 Security Dilemma Sandro 12/22/2008 1:30:01 PM 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

Re: Access 97 Security Dilemma Tom van Stiphout <tom7744.no.spam[ at ]cox.net> 12/22/2008 2:45:29 PM On Mon, 22 Dec 2008 05:30:01 -0800, Sandro <Sandro[ at ]discussions.microsoft.com> wrote: Provide the user with a shortcut, that includes the /wrkgrp switch to link to the appropriate MDW. -Tom. Microsoft Access MVP [Quoted Text] >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

Re: Access 97 Security Dilemma jacksonmacd <jackMACmacdo0nald[ at ]telus.net> 12/22/2008 3:20:42 PM 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 <Sandro[ at ]discussions.microsoft.com> wrote: [Quoted Text] >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 -- jackmacMACdonald[ at ]telusTELUS.net remove uppercase letters for true email http://www.geocities.com/jacksonmacd/ for info on MS Access security

RE: Access 97 Security Dilemma Sandro 12/23/2008 6:08:08 PM 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: [Quoted Text] > 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