Ty John
Terence
--- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@...> wrote:
>
> Terence-
>
> Yes, you can point some linked tables to one database, and others to a second or
> third database. BUT anyone who opens the linked tables must have full
> (including create) permission to the folder containing the database. You could
> put the unsecured tables in a folder where everyone has this permission. Put
> the "secured" tables in a folder where the permissions are only for people in
> the "secure" department. Make sure you give noone else permission to the
> secured folder - not even Read.
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Lahaina, HI)
>
>
>
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Terence
> Sent: Wednesday, February 01, 2012 12:38 PM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] linking to multiple databse's for the purpose of
> protecting tables
>
> Here is the situation, II am on a shared drive, permission an restrictions are
> accomplished via typical Windows Folder permission levels.
>
> The database I am building will eventually be split (back and Front), but I also
> have a need for a dozen tables to be shared with another department.
>
> I don't want them to have access to anything else but these dozen tables! Is
> there anything inherently wrong, or problematic with me linking my front end to
> more than one database?
>
> I'ts like I want 2 backends to contain tables. One set of tables is SECURE, and
> the other will Not be secure.
>
> Using access 2007
> Terence
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
Tidak ada komentar:
Posting Komentar