"Joan Wild" wrote:

> AR trout fisherman wrote:
> > Access security was established in a database when it was being
> > developed on an individual PC. Everything worked fine.
> >
> > The database has now been moved to a server.
>
> Did you move just the mdb or the secure mdw as well, to the server?
>
> > Local users log into the
> > db fine. When we log on to the server thru "Remote Desktop
> > Connection" we get on fine.
> > If you are logged into the server as Admin you can get into the
> > database. For any other server login, when we try to login to the
> > Access database we get a message we do not have the "necessary
> > permissions, see the administrator". The administrator says we have
> > all the permissions that are possible to give.
>
> The windows username shouldn't matter in this case.  It's just that when you
> log in as Windows Admin user, that user likely has the secure mdw set as
> their default, while other users have system.mdw as their default.
>
> All users need to use the secure mdw that was used to secure the mdb.  Put
> it on the server as well.  I assume that Access is installed on the server,
> since you are using RDC?
>
> Give each user a desktop shortcut with the following in the target:
> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
>
>
>

> Thanks Joan Wild
>
> Yes, Access is installed on the server and yes the MDW file had been
> transfered.
>
> As with a lot of things about computers we were trying to make
> something hard out of something easy! Long ago we had done the "Join"
> on the developement machines. When we did the "Join" on the server
> everything worked fine.
>
> Looks like I would have learned something after 25 years!
>
> Thanks again for replying to my post.
> --
> FKB
>
>
> "Joan Wild" wrote:
>
>> AR trout fisherman wrote:
>>> Access security was established in a database when it was being
>>> developed on an individual PC. Everything worked fine.
>>>
>>> The database has now been moved to a server.
>>
>> Did you move just the mdb or the secure mdw as well, to the server?
>>
>>> Local users log into the
>>> db fine. When we log on to the server thru "Remote Desktop
>>> Connection" we get on fine.
>>> If you are logged into the server as Admin you can get into the
>>> database. For any other server login, when we try to login to the
>>> Access database we get a message we do not have the "necessary
>>> permissions, see the administrator". The administrator says we have
>>> all the permissions that are possible to give.
>>
>> The windows username shouldn't matter in this case.  It's just that
>> when you log in as Windows Admin user, that user likely has the
>> secure mdw set as their default, while other users have system.mdw
>> as their default.
>>
>> All users need to use the secure mdw that was used to secure the
>> mdb.  Put it on the server as well.  I assume that Access is
>> installed on the server, since you are using RDC?
>>
>> Give each user a desktop shortcut with the following in the target:
>> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

"Joan Wild" wrote:

> It isn't always a good idea to join the mdw.  This'll make it the default
> workgroup file to use for *every* session of Access.
>
> That may be fine in your situation; as long as users only ever use your
> secure mdb.  If they have unsecured databases, then you don't want them to
> use the secure mdw for those.
>
> That is why it is recommended that you leave the default (i.e. join) as
> system.mdw, and use desktop shortcuts for your secure databases.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> AR trout fisherman wrote:
> > Thanks Joan Wild
> >
> > Yes, Access is installed on the server and yes the MDW file had been
> > transfered.
> >
> > As with a lot of things about computers we were trying to make
> > something hard out of something easy! Long ago we had done the "Join"
> > on the developement machines. When we did the "Join" on the server
> > everything worked fine.
> >
> > Looks like I would have learned something after 25 years!
> >
> > Thanks again for replying to my post.
> > --
> > FKB
> >
> >
> > "Joan Wild" wrote:
> >
> >> AR trout fisherman wrote:
> >>> Access security was established in a database when it was being
> >>> developed on an individual PC. Everything worked fine.
> >>>
> >>> The database has now been moved to a server.
> >>
> >> Did you move just the mdb or the secure mdw as well, to the server?
> >>
> >>> Local users log into the
> >>> db fine. When we log on to the server thru "Remote Desktop
> >>> Connection" we get on fine.
> >>> If you are logged into the server as Admin you can get into the
> >>> database. For any other server login, when we try to login to the
> >>> Access database we get a message we do not have the "necessary
> >>> permissions, see the administrator". The administrator says we have
> >>> all the permissions that are possible to give.
> >>
> >> The windows username shouldn't matter in this case.  It's just that
> >> when you log in as Windows Admin user, that user likely has the
> >> secure mdw set as their default, while other users have system.mdw
> >> as their default.
> >>
> >> All users need to use the secure mdw that was used to secure the
> >> mdb.  Put it on the server as well.  I assume that Access is
> >> installed on the server, since you are using RDC?
> >>
> >> Give each user a desktop shortcut with the following in the target:
> >> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
>
>
>