Front End / Back End Permission Headaches

[Joe Williams]

I have an app (less than 5 users) that I split into a Front End/Back End
configuration. The front end is stored locally and the back end is on the
network.I placed the back end in a hidden share and secured it with network
permissions, etc.

I then used the security screens to set permissions on the back end tables
for a group I created and removed the users group. Everything works great.

Then, I wanted to be able to stop people from just opening the back end and
browsing through the tables, even though they may have network permissions
to the back end.So, I ran the security wizard and secured the back end,
basically duplicating the permissions I set on the front end (removed users
group, added my custom group, etc)

Now the problem I am having is that if I log in as a member of the group I
created I get a "YOU DO NOT HAVE PERMISSIONS TO USE THE
\\SERVER\SHARE\DATA.MDB OBJECT"

I have verified that indeed that user/group has permissions in both the
front end and the back end. What could be the issue? Should I need to set
permissions on both the front and back end if I want to keep users from
opening the back end?

Thanks

joe

 

[Bill Mosca, MS Access MVP]

Joe

Check to make sure each user group has permissions within the workgroup to
open/run the database. You might have inadvertently removed that.

 

[Joe Williams]

Thanks Bill,

I had the right permissions set, my issue was that I used the database
splitter wizard to split the database and then tried to secure the back end
seperately. Obviously not the way to do it.

I found some instructions from Joan Wild to split the database manually and
that worked like a charm.

Thanks

joe

 

[Bill Mosca, MS Access MVP]

Joan's a keeper, alright.

Just FYI, I always manually split my DBs. In fact, I rarely start out with a
non-split DB. When I design, I do the tables first like all good little DBAs
should. <g>