M
Matthew Reed via AccessMonster.com
I've already successfully implemented Access security for a front end and
back end database, both mdb files. People run the front end mdb from their
desktop with links to a back end mdb on the network (standard). Now I'm
trying to add another pair of mdb files (a second application). The
workgroup file is on the network too.
Basically, when I run the Security Wizard to secure the second app, if I use
the existing workgroup, it still allows anyone in the Users group into the
database. If I build a new workgroup (I don't want to, but if it works, okay)
I get locked completely out of the database file -- I can't open it as any
user. I'm probably doing something wrong (Security Wizard?), but without
saying much more about the details of what I've done you probably can't help
too much.
Still, any tips on doing this, pitfalls, whatever? Can I use the same
workgroup or should I build a new one?
Thanks!
back end database, both mdb files. People run the front end mdb from their
desktop with links to a back end mdb on the network (standard). Now I'm
trying to add another pair of mdb files (a second application). The
workgroup file is on the network too.
Basically, when I run the Security Wizard to secure the second app, if I use
the existing workgroup, it still allows anyone in the Users group into the
database. If I build a new workgroup (I don't want to, but if it works, okay)
I get locked completely out of the database file -- I can't open it as any
user. I'm probably doing something wrong (Security Wizard?), but without
saying much more about the details of what I've done you probably can't help
too much.
Still, any tips on doing this, pitfalls, whatever? Can I use the same
workgroup or should I build a new one?
Thanks!