Unsecuring a secure Access Database?

[sausagefingers]

Hi,
having developed an access database to log Purchase Order discrepancies
for the company I work for, I have now been asked to make it available
for my work colleagues to use also.

I have learned the hard way that this is not an easy thing to achieve.

The database has served me well as a 'stand alone', 'single-user' tool,
I've never had any issues with it in the 18 months I've been developing
it.

The Database simply wasn't designed for a multi-user environment and as
you would expect it has suffered no end of problems since going 'live'
to my colleagues (in preliminary tests).

I have since re-written the entire db, splitting back and front ends
etc. trying to make it more robust and correct the errors and data
corruption I was experiencing.

However, I have never had to consider security issues with it up until
now and it seems to have me beat!

I have secured the back end (probably prematurely) and I can no longer
access it from the distributed front ends.

What I would like to do is start over, unsecure the database and start
again. I don't seem to know how to do this unfortunately.

I now have a fairly tight schedule to work towards and I really NEED
someone's help. If I can get back to where I was with it before I
secured it, maybe I can follow your precise instructions to set up user
and group permissions in a front/back end environment.

This stuff is all new to me guys so please offer any advice assistance
you can in order to help!

Thanks in advance.

Sausagefingers

 

[jacksonmacd]

To unsecure the BE, you need to grant all permissions to the Users
group. You should also ensure that Users group has all permissions to
everything in the FE. By doing that, any Access session will be able
to use any of the BE tables and FE objects. If you've secured the BE
by manipulating the various table permissions, you should be able to
find your way to granting all permissions to the Users group.

However, before trying that, if I were you, I would double-check that
I was launching each "distributed" Access session correctly. In
particular, I would double-check that I had copied the secure
workgroup file (.MDW) onto the network. Furthermore, I would check
that *every* distributed workstation was using that workgroup file by
using a properly coded shortcut. The target for the shortcut should
be:

"<fullpath to Access.EXE>" "<fullpath to frontend>" /wrkgrp "<fullpath
to MDW file>"

Here are a number of links about security:

http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#Security

 

[sausagefingers]

To unsecure the BE, you need to grant all permissions to the Users
group. You should also ensure that Users group has all permissions to
everything in the FE. By doing that, any Access session will be able
to use any of the BE tables and FE objects. If you've secured the BE
by manipulating the various table permissions, you should be able to
find your way to granting all permissions to the Users group.

However, before trying that, if I were you, I would double-check that
I was launching each "distributed" Access session correctly. In
particular, I would double-check that I had copied the secure
workgroup file (.MDW) onto the network. Furthermore, I would check
that *every* distributed workstation was using that workgroup file by
using a properly coded shortcut. The target for the shortcut should
be:

"<fullpath to Access.EXE>" "<fullpath to frontend>" /wrkgrp "<fullpath
to MDW file>"

Thanks so much, will check out the links in the morning after I have
digested the info you have provided.