Joining work group file (.MDW)
- Thread starter kstuart
- Start date
- Local time
- Today, 16:55
- Joined
- Feb 28, 2001
- Messages
- 30,140
As you asked the question specifically including workgroups, the answer is NO. Not if you wish them to have different rights depending on who they are.
On the other hand, you could surely determine their network name (search the forum for "network login name" and variants of that theme). You could set some flags based on who they are by having a startup screen with some code behind it. It is FAR more complex doing it this way when workgroup security is directly supported by Access.
On the other hand, you could surely determine their network name (search the forum for "network login name" and variants of that theme). You could set some flags based on who they are by having a startup screen with some code behind it. It is FAR more complex doing it this way when workgroup security is directly supported by Access.
Work group file
What if my security is being handled at the network level?
I did not create all these users in the database but instead gave permissions within Novell.
What happens is when a user who did not join the workgroup file enters the database, he is allowed to go from switchboard to switchboard but once he takes an option that opens a form or report, he receives
<<There was an error executing the command>>
I went to one PC and joined the workgroup and this solved the issue.
FYI, if a user is read only for the database at the Novell level, they receive a message when they enter the DB that they are read only.
I know it is not the best security but we are not talking sensitive data and this is only a temporary DB.
What if my security is being handled at the network level?
I did not create all these users in the database but instead gave permissions within Novell.
What happens is when a user who did not join the workgroup file enters the database, he is allowed to go from switchboard to switchboard but once he takes an option that opens a form or report, he receives
<<There was an error executing the command>>
I went to one PC and joined the workgroup and this solved the issue.
FYI, if a user is read only for the database at the Novell level, they receive a message when they enter the DB that they are read only.
I know it is not the best security but we are not talking sensitive data and this is only a temporary DB.
ghudson
Registered User.
- Local time
- Today, 17:55
- Joined
- Jun 8, 2002
- Messages
- 6,194
You do not have to join the users computers to the workgroup file. Actually, they would prefer that you do not join them or else they will have to login just to open a new database.
The best way to have a user open a secured db is to put the security info in their shortcut. This is a working example...
"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "C:\Testing\TESTWorkgroup.mdw" "C:\Testing\TESTdb.mdb" /user TEST User
The first part states the location of the Access program, next is the workgroup switch, then the location of the sercured workgroup file, then the location of the database and the user switch with the users workgroup name.
HTH
The best way to have a user open a secured db is to put the security info in their shortcut. This is a working example...
"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "C:\Testing\TESTWorkgroup.mdw" "C:\Testing\TESTdb.mdb" /user TEST User
The first part states the location of the Access program, next is the workgroup switch, then the location of the sercured workgroup file, then the location of the database and the user switch with the users workgroup name.
HTH
O
osvalch
Guest
Great, very useful. You have saved me from some hours of work.
Similar threads
