I have the security set via the Access workgroups for both groups and users. I want to be able to use the username entered on the logon screen to filter my query results.
How can I get the logon id that was entered when my switchboard form opens?
I'm trying to put in place a workgroup and I'm struggling with it at the moment. I created a seperate workgroup and have a command line short cut to it. When I try to add a user to the admin group permissions it works fine except that I can't open any of the forms in design mode. It says I do not have exclusive rights . I dont know what to do. I though that the admin password would be set to blank but It won't open the database either.
I have successfully created my own private workgroup and have set up security levels for 4 users on one access programme that l have written.
I have a second access programme that l use with the same users, however l want to set different user parameters, can l set a second workgroup up as l did the first.
I currently have several Access 2003 databases on my computer. I have been working on a new one that must be secured.I have created a new .mdw file to handle this. The path to this file is included in the shortcut. Everthing works great.
HOWEVER:
Whenever I close this database and then open another, it is still promting me for a password (the other DBs aren't supposed to be secure). I have changed the shortcuts to go through the old system.mdw but it still does it. When I change the workgroup manually, the secure database no longer prompts me for a password. It would appear there is more to selecting the workgroup than just editing the shortcut.
I'm trying to set-up and secure a networked multi-user database. I used the Workgroup Administrator to create a new workgroup and save it to the network drive. However, when I open my database, it seems it may still be pointing to the the default SYSTEM.MDW workgroup on my hard drive. Do I need to do something to my database to tell it to point to the new workgroup I have set-up? When I start having other people log in from different locations, will they need to join the workgroup or also point the database to the networked workgroup when they open the database? The manuals aren't very clear on this, please help.
Can someone post a copy of a sample mdw file so that I may observe the design of the database? I am very new to the concept of db security and would like to take a look at how the design is constructed. Thanks!
We have an old Access 97 database with a workgroup file. The problem was that the machine was upgraded and the software was changed to XP. They support guys moved all files to the new PC except the the workgroup file. We can't fine a backup of the w/g file.
I am unable to upgrade the database to access 2002 because of the permissions.
What is the easiest way to get past this stumble block.
We are running two versions of Access (97 and 2003) on some of our machines. We recently set up a new workgroup file, but it seems that on the machines that have the two versions of Access the workgroup file reverts back to the old setting everytime the user logs in again. What do we need to do to prevent the workgroup file from switching back?
Present Go to user computer, and then manually to join the workgroup.
Is this possible?
Send email to new user. Join workgroup using a zip file. When file is un-zip the user automatically joins the workgroup and places a short cut on there desktop.
I would like to link to a table that is not in the same workgroup as the database I am working in. Both databases are from different departments - I only want read rights to the linked table to run queries against some data in my database. I have access to the database I am trying to link to - but have not been able to figure out a way to do this?
This is more of a point of interest then a question, at work, Access defaults to a central workgroup file, so all Access files opened on a work machine will prompt for a user name and password, and only let you in if you get it right... but if you move the work group file, even after it has been open using that workgroup file, it will just let you straight in and GIVE YOU ADMIN RIGHTS!
No one really seems to know about this... does it happen if you manually set the workgroup file? Or is this just a security hole if you rely on the default? I'm not sure yet, haven't tested, but i fell people should be made aware (happens for sure on Access2002, haven't tested it on any others)
I was looking for free access add-ins through a search engine when I came across this site. I'm not sure whether or not some of the more seasoned programmers have seen this, but so far it looks like a less confusing alternative to the security features that access comes with. I'm not in any way advertising this, and I haven't tried it myself yet, so I can't speak about how good or bad it is, but it may be something worth looking into. Here are the links:
http://www.accesswizards.com/Downloads.html This lists the add-ins that are available from this particular site.
http://www.accesswizards.com/SecDetails.html This is the "read me" information about the security add-in.
Is there any function or code that would display the workgroup in which the current user belongs simular to the function "currentuser()" which displays the user logged onto the db?
I've set up security on my database before with great success, and now I'd like to use the same workgroup file (a copy with a new name and location) to secure a nes db.
I open the new db, and join my earlier created mdw file. I'm prompted with that I have joined my workgroupfile.
I then set permissions for each user in the workgroupfile, remove admin rights for the admin user account, and assign admin rights to my own account. I am also the owner of thr db.
I now run the security wizard, and I make no changes to any checkboxes.
This goes nicely, and the wizard closes after making a backup file.
I now want to re-join the system.mdw file, so I don't get prompted with the logon dialog when opening a new db or an unsecured db.
If I now try to start my new secured db by double-clicking on the secured mdb file it opens ?????
I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups. The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set. How can I make the database file bound to the MDW file, so that it does not open without it.
I am trying to setup User Level Security around a Purchase Order Database that I created. Using the Wizard I was able to setup different users with different permissions.
However, as I found out the hard way (but I did recover it), 'joining' a PC to a my new security workgroup forces all Access databases on the PC to use this.
Is there a way to force just this one Access .mdb file to use the newly created PO Workgroup security file ?
I am aware of setting up a shortcut to point to thesecured db. Ie: "C:Program FilesMicrosoft OfficeOfficemsaccess.exe" /wrkgrp "C:PO FormsMyWorkgroupFile.mdw" "C:PO FormsMyDB.mdb" /user
But despite the above shortcut, couldn't users just find out where it points to (by looking at the Properties of the shortcut), and open the .mdb file based on that ?
I recently created a workgroup for an access database and it works fine. But I have other versions of that same database (beta copies) for which I didn't create that workgroup file. They have different names than the first DB for which I made the workgroup. But even when I open those beta copies it still launches the workgroup file (system.mdw) and prompts me to login. What do I need to do to revert these changes and go back to the unsecured version of my database?
I've designed an access ade file (based on sql server) and distributed it at the network.
Somebody else has made another database (mdb) and placed the users in a access workgroup file by placing their windows logons into the workgroup file. These users happen to be the same users accessing my application. The following thing is happening : "when the users open my database they are prompted their user names and password of the workgroup file'.
I placed an empty database and the same thing is happening, the workgroup security is active alongside every database deployed to this specific user group.
How can I easily 'tell my database' it shouldn't make use of the workgroup security?
(It's odd that an ade which isn't able to use workgroup security prompts users by using workgroup security)
I cant seem to get a certain setting right. I am trying to setup a user for the database that I have been working on. It keeps saying the following:
"It says I do not have necessary permissions to open. Have the system admin. Or person who created the object establish appropriate permissions for you."
I have that person assigned to the following:
Full Permissions Full Data Users Updated Data Users
And they still are unable to open the database.
Now from what I have read on this forum, I shouldn't give any personal permissions. So I have assigned users to groups and given the groups permissions.
In regards to the security question, what are bare minimums for a user to open the database, use the switchboard, choose a form, enter/change data via the form, and view reports.
I dont know the difference between:
Open/Run Read Design Modify Design Administer
And I am afraid to give more than what I need, and I feel like I am just guessing and hoping to set it right. Thanks for any direction in this area.
I've created a duplicate of our database in order to be able to work on the design of it from several locations. At present the database which is being used has been split into FE (on local machines) & BE (on server), with a .mdw file for the workgroup settings.
For the duplicate I have created a new database with all the Tables, Queries, Reports, Forms, Macros and code copied from the FE & BE files into a single file. My question is, to be able to work on this from remote machines / pass it on to others to work on the design, do I need to have a copy of the MDW present with the duplicate, or is it possible to remove the workgroup and security permission settings?
First of all, I'd like to thank everyone who's a member and has helped someone at some point within the forums! I'm quite new to Access and have received a massive amount of help on one of my first databases.:)
As the title points out, I'm not sure about the WIF. If I have two database in the same location, lets say their called DB1 and DB2 and I create a WIF for DB1, this wont affect DB2, will it? For example, it wouldn't create security for DB2?
Another senario is, if I have two databases nameed DB1 (basically one is a copy) within lets say two different subfolders within the same top level folder, because they are the same name, would this mean that they would both be affected by the same WIF?
I recently created a WIF like this and had to enter a password for both databases! to my consternation, I deleted the DB (along with the WIF) with which I made up the WID and I could access the Other DB without the Password! If I do create a WIF for a database, how can I stop using it as if I never created it in the first place?
Is there anyone out there that can help me with this problem. I want to create a hyperlink in MS Outlook to my database file using my workgroup. The problem I'm having is when I put the following: file://"N:DbaseFilesSCC_Dbase.mdb" that works. It will open Access to that dbase file. But if I include the workgroup file associated like this: file://"N:DbaseFilesSCC_Dbase.mdb" /WRKGRP "N:DbaseFilesCSS_Issues.mdw" it doesn't work. Can someone please tell me why. I've been struggling with this for days now. I can't find any solutions.