system.mdw

[Ian Davies]

Hello
I have some questions about Access security
1) If I have secured a database and want to distribute it will I have to
distribute the workgroup file (system.mdw) and install it in the system32
dir of the users computer.

2) How will this affect any security they may already have and a system.mdw
file that may already be in place on their computers

Is the security data on the mdw file specific to the database I created it
from or to any databases opened or created there after on that installation
of Access

Ian

 

[Lynn Trapp]

1) If I have secured a database and want to distribute it will I have to

distribute the workgroup file (system.mdw) and install it in the system32
dir of the users computer.

You need to split your database. Distribute a copy of the frontend to each
user. This application will be on the user's hard drive. Place the backend
AND the workgroup file (name it something other than system.mdw) in a folder
that all users have full access to.

2) How will this affect any security they may already have and a
system.mdw
file that may already be in place on their computers

Use a shortcut that references the secure workgroup file and you should see
no effects.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Ian Davies]

Thanks for your response

Not that it matters by the sound of it, my front end is a Visual Basic App

If the system.mdw file I created to secure my Access backend was created in
my PC's System32 dir. Would any kind of link between it and the database
break down if I
1) rename it
2) distribute it and have it installed somewhere other than the directory it
was originally created in?

Ian

 

[Lynn Trapp]

my PC's System32 dir. Would any kind of link between it and the database

break down if I
1) rename it

As long as your VB frontend is pointing to the right file, you should be ok.

2) distribute it and have it installed somewhere other than the directory
it
was originally created in?

Well, unless all your users have full access to your PC's System32
directory, you will have to put it somewhere else. The most common approach
is to store it in the same folder that your backend resides in.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Ian Davies]

Thanks Lynn for your help
One more

Well, unless all your users have full access to your PC's System32
directory, you will have to put it somewhere else. The most common approach
is to store it in the same folder that your backend resides in.

If original path was

d:/SomeDirectory/ApplicationFolder/MyBacked.mdw

by the installation dir was of the users choice lets say

server1:/Applications/ApplicationFolder/MyBacked.mdw

wouldnt this mess things up or like many programs it routinley looks in, or
assumes the mdw file is in the application path?

Ian

 

[Lynn Trapp]

If original path was

d:/SomeDirectory/ApplicationFolder/MyBacked.mdw

by the installation dir was of the users choice lets say

server1:/Applications/ApplicationFolder/MyBacked.mdw

wouldnt this mess things up or like many programs it routinley looks in,
or
assumes the mdw file is in the application path?

Typically you will want to use the UNC name for the path:

\\servername\Applications\ApplicationFolder\MyBackend.mdw

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html