> I am in the process of creating a simple split flat database using the
> Splitter Wizard.  I shall locate the back end in a shared folder on
> the network and ensure the six users each have a copy of the front
> end database in their respective folders.  Each user types data into
> their own table (I know this is not best practice but that is what
> was decided!)
>
> I understand the backend has to be stored in a shared folder which
> all the users have permission to use.  Given this requirement, how
> can I ensure that the users cannot open the backend database?  I have
> heard a bit about passwords etc and that they can cause problems.
>
> I am using 2003.
>
> I am a sophisticated user of Access but not a programmer.

"Joan Wild" wrote:

> If you do not want to implement Access security, you can
> - create an Autoexec macro in the backend with two actions
> first - Msgbox with a message telling them to open via the frontend (or
> something)
> second - Quit - which will close the database
>
> Your users may know about the shiftkey bypass, which would bypass this
> autoexec macro.  If that's the case you can disable the shiftkey bypass.  Of
> course, your users may know how to re-enable it.
>
> You can also put the backend file in a hidden share \\server\share$ rather
> than \\server\share. That'll hide it in Windows Explorer, so they're not
> likely to find it.  They would have to know the actual path to locate it.
>
> These measures may be sufficient for your situation.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Mary Ann wrote:
> > I am in the process of creating a simple split flat database using the
> > Splitter Wizard.  I shall locate the back end in a shared folder on
> > the network and ensure the six users each have a copy of the front
> > end database in their respective folders.  Each user types data into
> > their own table (I know this is not best practice but that is what
> > was decided!)
> >
> > I understand the backend has to be stored in a shared folder which
> > all the users have permission to use.  Given this requirement, how
> > can I ensure that the users cannot open the backend database?  I have
> > heard a bit about passwords etc and that they can cause problems.
> >
> > I am using 2003.
> >
> > I am a sophisticated user of Access but not a programmer.
>
>
>