I have just set up a fairly small database for use across two separate sites.
It has been split, with the front-end saved in the same location as the
back-end. This shouldn't cause any problems with corruption, as the drive is
backed up every night, and usage will not be high. Each user has a shortcut
to the front-end on their desktop. I want to limit the access to the
back-end, to stop anyone from altering the design of the tables, forms,
reports etc except for me and one other user/administrator. If I put the
user-level security on the back-end, will the front-end pick it up and apply
the same user-level security to the front-end? Or should I apply the ULS to
the front-end only? I don't want to spend a lot of time doing something and
finding it was a waste of time.

"Anne Boyce" <(E-Mail Removed)> wrote in message
news:CA9925E8-4281-4CDC-9571-(E-Mail Removed)...
>I have just set up a fairly small database for use across two separate
>sites.
> It has been split, with the front-end saved in the same location as the
> back-end. This shouldn't cause any problems with corruption, as the drive
> is
> backed up every night, and usage will not be high. Each user has a
> shortcut
> to the front-end on their desktop. I want to limit the access to the
> back-end, to stop anyone from altering the design of the tables, forms,
> reports etc except for me and one other user/administrator. If I put the
> user-level security on the back-end, will the front-end pick it up and
> apply
> the same user-level security to the front-end? Or should I apply the ULS
> to
> the front-end only? I don't want to spend a lot of time doing something
> and
> finding it was a waste of time.

You need to apply security to both the front and back ends. If you expect
more than one concurrent user, give each user their own copy of the FE. BTW
your BE should contain *only* the tables, your FE everything else plus the
linked tables.

Regards,
Keith.
www.keithwilby.com