Security Issues - mdw file

  • Thread starter Thread starter JimBob
  • Start date Start date
J

JimBob

My database is secured on a shared drive with all of the security in
place. Each user has their own id and password and the only way that I
could get to that point was to create an mdw file to the shared drive
and have all users join that workgroup. Now the issue is that whatever
access 2002 database they attempt to open, they must use the ID and
password.

I had written earlier regarding this issue and was informed that I
could specify a network drive for a local .mdw file as in the example
below:

"C:\Program Files\Office2K\Office\msaccess.exe"
"\\Server\Share\DatabaseName.mdb" /wrkgrp
"\\Server\Share\secacc.mdw"

I few questions that I need clarfication on since I am treading
dangerous ground here. I can create databases and make them look
pretty and functional but this security issue is driving me nuts...

1. Where do I creat these command lines, within the database that I
want to share under the macro section or does this have to be done via
a VB script?

2. If I am sharing the mdw file off my local PC, does that require my
PC to be available 24/7? I'd rather not do this and just have the
users log in to use any Access database. This would please our
auditors to no end since it is a requirement that all databases be
secured.

As you can tell, I have some knowledge in this regard but this security
issue is holding up from releasing the database to production.

Thanks!!
 
JimBob,

It would have been better for you to maintain the original thread you started on 12/12
with the subject "Security issues - AARRGGHHH!!!" I flag messages that I reply to, and
these are sorted at the top of my view by date.

You don't want to join the users to the new .mdw file. This is what is now causing all of
them to have to enter an ID and password for any database they work on. I can imagine
that they're not real happy about right now. Rejoin each of them back to the standard
system.mdw file.
1. Where do I creat these command lines, within the database
that I want to share under the macro section or does this have
to be done via a VB script?
Click to expand...

None of the above. Create a SHORTCUT to your database. Right-click on the shortcut and
then left-click on Properties (I'm assuming you have not switched your left and right
mouse buttons). Edit the shortcut's target, so that it includes the correct path to
MSAccess.exe on each PC, your database on the server, and the workgroup information file
on the server. I recommend using the UNC convention (ie. \\server\share) instead of a
mapped network drive. For example:

(watch for word wrap here)

"C:\Program Files\Office2K\Office\msaccess.exe" "\\Server\Share\DatabaseName.mdb" /wrkgrp
"\\Server\Share\secacc.mdw"

You are limited to 256 characters total, so you may need to place your database in a
higher level directory to avoid excessively long paths. Actually, this is a good idea
anyway, since you can take a performance hit if your database is several levels down from
the root directory.
2. If I am sharing the mdw file off my local PC, does that require
my PC to be available 24/7? <snip>
Click to expand...

You don't want to do that. Place your .mdw file on the server.

Tom

___________________________________________


My database is secured on a shared drive with all of the security in
place. Each user has their own id and password and the only way that I
could get to that point was to create an mdw file to the shared drive
and have all users join that workgroup. Now the issue is that whatever
access 2002 database they attempt to open, they must use the ID and
password.

I had written earlier regarding this issue and was informed that I
could specify a network drive for a local .mdw file as in the example
below:

"C:\Program Files\Office2K\Office\msaccess.exe"
"\\Server\Share\DatabaseName.mdb" /wrkgrp
"\\Server\Share\secacc.mdw"

I few questions that I need clarfication on since I am treading
dangerous ground here. I can create databases and make them look
pretty and functional but this security issue is driving me nuts...

1. Where do I creat these command lines, within the database that I
want to share under the macro section or does this have to be done via
a VB script?

2. If I am sharing the mdw file off my local PC, does that require my
PC to be available 24/7? I'd rather not do this and just have the
users log in to use any Access database. This would please our
auditors to no end since it is a requirement that all databases be
secured.

As you can tell, I have some knowledge in this regard but this security
issue is holding up from releasing the database to production.

Thanks!!
 
Back
Top