> Obviously I've messed something up here: could some kind soul point me in
> the right direction?

I strongly recommend that you obtain a copy of the Access Security FAQ
(available at http://support.microsoft.com/default.aspx?scid=kb;[LN];207793) and
read it thoroughly - more than once even. If you don't follow the steps in the
FAQ *exactly* then your security will not be properly implemented.

--
Bruce M. Thompson, Microsoft Access MVP
(E-Mail Removed) (See the Access FAQ at http://www.mvps.org/access)
>> NO Email Please. Keep all communications
within the newsgroups so that all might benefit.<<

As Bruce said, you need to read more on the subject. It is not all that
easy. In fact you did not indicate a thing about securing the new database.

Access security is a hard learning curve, but once you get there, it is
very useful.

Unless you "secure" the other databases, they will remain available to
anyone. They will be open to anyone who does or does not start Access in
secured mode.

Note: What exactly does you boss want "..requested that users log in"
can mean many things. Does he want to track everything they change?

If all you need is to protect the data from changes, you can accomplish
that several other ways.

--
Joseph E. Meehan

26 + 6 = 1 It's Irish Math


"Alan Greenwood" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> My users have quite a few Access 97 databases (on a Novell 5 network) for
> which no login is required. I have a new database for them where the boss
> has requested that users log in. I hope to be able to obtain a situation
> where they only have to log in to the new system, and old databases are
> still available without them having to enter a password.
>
> I created a NEW.MDW file on my own machine with the required groups and
> permissions and it worked fine on my computer. I then put the MDW file
onto
> the network (in the same directory as the database) and put a shortcut
onto
> a user's Desktop which referenced the MDW file using the /wrkgrp command
> line parameter, and following that with the full path to the MDW file. I
> had hoped that this would mean that users would have to log into the new
> system (via the settings in the referenced MDW file) but there was no
> password box: all users got in straight away but only as ordinary users
> with minimal permissions.
>
> Obviously I've messed something up here: could some kind soul point me in
> the right direction? We use Office 97 on NT4 workstations on a Novell 5
> system. Thanks a lot in advance to anyone who can help.
>
> -----------------------------
> Spam-buster: remove the XYZ!!
> (E-Mail Removed)
> -----------------------------

> 26 + 6 = 1 It's Irish Math

Bottoms Up! <chuckle>

--
Bruce M. Thompson, Microsoft Access MVP
(E-Mail Removed) (See the Access FAQ at http://www.mvps.org/access)
>> NO Email Please. Keep all communications
within the newsgroups so that all might benefit.<<

My users have quite a few Access 97 databases (on a Novell 5 network) for
which no login is required. I have a new database for them where the boss
has requested that users log in. I hope to be able to obtain a situation
where they only have to log in to the new system, and old databases are
still available without them having to enter a password.

I created a NEW.MDW file on my own machine with the required groups and
permissions and it worked fine on my computer. I then put the MDW file onto
the network (in the same directory as the database) and put a shortcut onto
a user's Desktop which referenced the MDW file using the /wrkgrp command
line parameter, and following that with the full path to the MDW file. I
had hoped that this would mean that users would have to log into the new
system (via the settings in the referenced MDW file) but there was no
password box: all users got in straight away but only as ordinary users
with minimal permissions.

Obviously I've messed something up here: could some kind soul point me in
the right direction? We use Office 97 on NT4 workstations on a Novell 5
system. Thanks a lot in advance to anyone who can help.

-----------------------------
Spam-buster: remove the XYZ!!
(E-Mail Removed)
-----------------------------