all groups > dotnet security > april 2007 >
You're in the

dotnet security

group:

workgroup information file and remote users


workgroup information file and remote users DinosRose
4/19/2007 4:28:02 PM
dotnet security:
I'm reading through the general help file on user-level security and it
indicates that when a person logs on using their password, "Access then goes
out and reads a workgroup information file". Does this mean that the user
needs access to where I save the workgroup information file when I'm using
the Wizard? And if the user isn't connected to the network where this file
is saved, can they not access the database? At this point I'm trying to
determine the most appropriate security measure for our database
applications. Thanks!
--
Re: workgroup information file and remote users Nicole Calinoiu
4/20/2007 12:00:00 AM
I haven't used Access in a while but, assuming things haven't changed much,
answers are below. (You might want to confirm by posting in an Access
newsgroup.)


[quoted text, click to view]

You can move the file after you finish using the wizard, but the user will
require read permission on the final location of the WIF file at runtime.
You can specify the location of the file via the "Jet OLEDB:System Database"
connection string property.


[quoted text, click to view]

If the database is also on the network, then not having access to the WIF is
presumably the least of your worries. ;) If you are distributing the
database onto client machines, then it's typical to distribute a copy of the
WIF along with it.


[quoted text, click to view]

Access user-level security is a rather weak authorization mechanism that is
fairly easy to bypass. If you're serious about security, you might want to
consider using a database server like SQL Server rather than a file-based
database like Access.


[quoted text, click to view]

AddThis Social Bookmark Button