Re: Split Database Security Problem
- From: "Br@dley" <brad@xxxxxxxxxx>
- Date: Thu, 22 Dec 2005 22:49:15 GMT
carriolan@ wrote:
> Hi
> I have managed to secure a split database. Both frontend and backend
> share a common workgroup, common security groups and common users and
> permissions, but as in all good stories there is a catch.
>
> All works well for the newAdmin user, but not so for the newUser. In
> the AutoExec macro I have a call on some VBA to reconnect the frontend
> and backend databases. It does not reconnect for the newUser. My
> conclusion is that the security permissions are not generous enough to
> permit reconnection! The newAdmin for the 'object database' has the
> following permissions: Open/Run, Open Exclusive and Administer. The
> newUser only has: Open/Run, Open Exclusive on the 'database object'.
> The backend dBase only contains tables which are linked to the
> frontend.
>
> How do I set the permissions to get the frontend to auto reconnect to
> the backend please?
>
> Regards
> Carriolan
You need to give the user design permissions to the linked tables in the
front end. They will not be able to change the table design if you
maintain no design permissions in the back end.
--
regards,
Bradley
A Christian Response
http://www.pastornet.net.au/response
.
- Follow-Ups:
- Re: Split Database Security Problem
- From: carriolan@xxxxxxxxxxx
- Re: Split Database Security Problem
- References:
- Split Database Security Problem
- From: carriolan@xxxxxxxxxxx
- Split Database Security Problem
- Prev by Date: Re: Using seek to find if a record exists
- Next by Date: Re: A2K3 & object dependency refresh
- Previous by thread: Re: Split Database Security Problem
- Next by thread: Re: Split Database Security Problem
- Index(es):
Relevant Pages
|