Split Database Security Problem

[carriolan]

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

[Anthony England]

<carriolan@> wrote in message
news:t1********************************@4ax.com...

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

Log on as admin and link the tables manually. Temporarily comment out the
code which does the re-linking. Log in as user. Does everything else work
OK? Forms, tables queries, etc?
If the answer is yes, then it would appear to be only the re-linking
routine. Does it refresh the links or delete and re-create them? You will
probably need to assign more generous permissions to the front-end linked
tables - eg let standard users alter the design of them so they can be
re-connected and don't worry - those permissions are only on the linked
table - they couldn't change the design of the real back end tables.

[Steve]

In addition to Anthony's comments - does newUser have Read permissions
to the folder where the the backend resides on the server? Also, does
newUser get an error message when your VBA relinking code executes, or
does it just fail to link properly? If there is an error message,
please post its contents.

[Br]

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

[carriolan]

Hi Anthony, Steve and Bradly

Thanks for your help. I amended the frontend permissions, as you
suggested, for the backend tables. It worked like a dream. Thanks +
Merry Xmas
--
Regards
Carriolan
On Thu, 22 Dec 2005 22:49:15 GMT, "Br@dley" <br**@usenet.org> wrote:

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.