Daniel Dickover said:
I have mostyly set up the security on my database and I have one more
question at the moment. We are currently on a network and we have a
computer that is at another site.
I assume this remote site is accessing it via Terminal Services or similar,
and not directly over the WAN.
How do I ensure that all sessions will be logged onto the correct
workgroup? Do I place the workgroup on all the possible workstations that
users can use?
You could do that, however it is not easy to maintain. Passwords are stored
in the mdw. What if a user goes to a different machine? Or what if you
have made changes to the mdw? You'd then need to copy it to every
workstation (thus overwriting their password).
Or should I place the workgroup on each user's personal network drive?
Same issue. You can just have one copy of the mdw in a shared drive.
Currently I have the DB and workgroup on our department's drive. When I
logged onto a remote computer and gained access to our department's drive it
did not log me on to the new workgroup.
That suggests it was not secured properly to begin with. You would have
been accessing it using the default system.mdw. You shouldn't have been
able to even open the mdb. Follow all the steps outlined in the security
FAQ
http://support.microsoft.com/?kbid=207793
So the question is do I copy the workgroup on all my dept member's
personal drive and join them to the group?
You need to first ensure that it is secured properly. Then your remote user
needs to run it via Citrix or Terminal Services - running it directly over a
WAN will definitely result in corruptions.
Finally you should split the mdb into frontend/backend. Keep the backend
and the mdw on the server in a shared folder. Give each user a copy of the
frontend on their workstation. For the TS user, put the frontend in their
folder on TS.
