We have added a new user, following the steps that we always follow, with no probs upto now.
He's showing in the list of users with membership of the correct groups.
However when trying to login with his username and password although it looks like it's accepting username and password as normal and database begins to open we then get the following error message
Using Access's User and Group Accounts or Using a Login Form to access database?
I've been researching on how to make a database secure. How to create User and Group Accounts on access, I see the step by step instructions and tried it out myself.
I also saw some sites where they give an example of a Login Form and how to create one.
My question is do you need to create both. First create the users and groups to permit or deny access to certain forms and then have a login form?
But would that mean that they'd have to login twice? Once when the database opens because it activates the db security that was created and then login again in the login form that was created?
Also when the user logins in and clicks on the cmd button on the form which opens up another from, frmWorkLog, I have an Employee field. This field I want it to have the user's name entered automatically and "locked". So that info, employee name, is extracted from the user's login. So then the user can only see his or her records only and no one elses.
How would I go about creating that. Hope I made my explanation clear.
I have a multi user database in Access 2000 that is on a server. The individual users have shortcuts pointing towards the server instance. One user and one user only when opening the shortcut gets the error "you do not have exclusive rights to the database" .
All other users can enter the database with no error box. I have checked the advanced setting under options and they are correct. Ironically if you go to start and open access then navigate to the database shortcut. It opens with no error.
I stumbled upon the Option Group function just yesterday and, happy as a clam, I created a group with 2 options in radio button style. I assigned the values to a field called Registration_Type as the 2 options are "Confirmed Registrants" and "Prospective Attendees".
[Great. That part works well. When I look at the table, a 1 or a 2 is in that field so it's great to know how to control accidental ticking of radio buttons (previous 450 records or so didn't have this option group functionality so one might easily tick one of the buttons. So one part of controlling option group I know I can handle via the table itself for now.]
The challenge is how to ensure the user always ticks one or the other ... I went back to the main table and tested the 'required entry' option for the Registration_Type field but forcing an action like this is not ideal in my mind. The usual error message vagueness for the average user is no good and I don't want to limit the user so much.
Is there a way to simply have a popup come up warning that neither radio button was ticked? Perhaps something linked to the form - i.e., maybe "after update"?? I only learned about attaching code to before and after update on controls a couple of days ago, so not sure if this would be best approach.
Just something to let the user know that nothing has been ticked in the option group as that controls in which of 2 reports the data will show up in so any record not ticked might mean a registrant being left out, which would be rather disastrous <g>.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I've created a database and I now need to set up user accounts for access to it, so that I can restrict who has read only and who has write only permissions.
I've done this before and never had a problem! But this time, whenever I try and create a new account, the following message is displayed:
Cannot update. Database or object is read-only.
Can anyone help as to why I get this message and what I can do to stop it! Whilst it does this, I can't create any user accounts.
I created a database for multiple users, it seems only one user can be in database at a time. Is there a property that allows multiple users to simultaneously use database. My record locks property is no. Is there some other property that needs to be set ??
i have build a single user application in access 2010. now i want to build multi user application and want to deliver to end user.how can i make my all vba code safe from end users.
We are encountering severe performance problems when running our access database on our Network.
Symptom:
Huge drop off in performance when 2nd and subsequent users refresh links to chosen back end database. If the database is opened by another users front end database.
Takes up to 10 minutes to refresh the links to 120 tables in Back-end MDB database.
The system is designed as a split front and backend Access database. The back-end Data MDB database is located on a Windows 2000 server.
The first time a user logs on they are required to locate and Re- Link the tables from the back-end database which holds data for the current year. If they wish to work on another year they re-link the tables from the relevant back end database.
When running locally the Front end takes between 5 and 10 seconds to refresh ALL the links to around 130 tables.
When the back end is on a network drive the process takes about twice as long. But is still quick.
If another user has the file open via their own (locally held) front end, then the refresh link process takes between 5 and 10 seconds PER TABLE !!
This means that that it takes up to 10 minutes to complete the re-link. Same behaviour if using Linked table Manager or refresh links using code
As soon as second user logs out of database the refresh link process speeds up.
The behaviour has been observed on a variety of servers and customer networks.
General data access is also much slower after 2nd user - but just about bearable. Data files are small – few records – occupy 7mb on disk.
Development Platforms – Windows XP / 200 clients, Windows 2000 Server hosts the back end database.
Front end is Access XP (MDB or MDE File) with al the latest service packs and security updates installed.
We have experienced this problem with a number of different systems running in various environments. But this wasn’t a problem with the old Access 1 database
HELP! Access should be able to support 10 – 20 users - we can barely run 2!
I am using a Access database with a frontend/backend design. I want to keep a table in the BE updated with the current list of users inside of the frontend. To do this I thought that I would just have the front end update a time field saying that that user is still inside of the FE. My question is two-fold - firstly, how can I run a function every minute or so to update this table.
I am developing an Access database, and using the Access 2007 Developer Extensions to "compile" it into an installable program which includes the freely distributable Access 2007 RunTime, for users who don't have it already installed.
I am planning on charging a subscription fee to use my Access database. Are there any existing method for handling making sure the user's subscription is still active, and if not, either locking them our or preferably making everything read-only? If there aren't any existing methods anyone can point me to, does anyone have any ideas?
I plan on being the person who installs the application the first time, however I'm sure instances will come up where I instead mail the user a CD for them to install.
Regardless of whether I complete the first install, I'm not interested in going to each users' location periodically regarding the subscription.
I'm more interested in going the route of the user typing in some type of registration code, which is validated for read/write access for a period of time.
I don't want to rely on the user having an internet connection, but if they had one, I could certainly go the Microsoft model (try internet verification, if it goes wrong or there isn't a connection, have user call in.)
If I want to distribute a front end to connect with a MySQL back end ... do I need to set up the system DSN on each workstation that will be using the front end?
I am currently looking into some of the security aspects of Access, as I am still not yet sure how i'll be designing a new database program, (whether to use Delphi to link to the database or run the database through Access itself) however, I was wanting to look into the security aspect of Access itself as part of my education and decision making process. Now I have deduced (correctly?) that some of the user/group access rights are based on the NT/2k/XP User/Group permissions etc, yet I was wondering if there was a little more to it than that.
In some ways I would like the application (through access or otherwise) to initialize with a logon prompt, that would ask for username and password. The database would internally?? retain the password information for security rights. I'm not sure if i'm thinking this through correctly, so i decided to come here for a few pointers in the right direction. I'd like to set up internal to the database a set of groups and users with different levels of security. I don't want them based on the XP user account passwords and such, but just an internal database login. This would allow, to some degree, a specific master group to add / remove users from the database, as well as control user access rights to the database internally. More or less, I want the database itself to be self-contained with all security and access rights, instead of basing them off of some external NT based security information. So to my actual questions:
Is this possible? Where would I start looking to set this up?
Hi, I have put my database in a package using MS Access extension but the user and Group Perssion is not included to the package. Does some one know how to include the permissions too.
This is a database that uses user-level security setup in Access 2003 but it is being run on 2010. An update to the security system is in the cards in the near months, but right now I need to add one more user and I am having an issue with that.
I can add the new user in the user and group accounts form and I can add him to any group except for one. Unfortunately that is the group that he needs to belong to. You can see in the attached image the new user (jschiff) and the group I want to add him to. There already are some other users in that group. What could prevent me from adding this new user to that group?
I have to change a group membership of one user in an multi user access database. As I see its no possibility to change it in the backend (in X.ldb file) nor in frontend.
I moved my access database and not my user account do not have privelages. However, the group accounts they are linked to have been set-up correctly. Why would my group account privelages be ok, but when I look at each user individually they have no privelages set. I'm confused as to why this would be if the users are in the specific groups I have set-up.
Hi all. Stumbled onto this forum during a google search.. looks like a great forum.
I have a question. this thread http://www.access-programmers.co.uk/forums/showthread.php?t=124689
goes into a simple function to group by the name and add their total.. however what i need to do is that plus have a user input of the date.
eg of the table
Date Title Invoice 02/02/07 ABC123 11.00 02/02/07 ABC123 12.50 02/02/07 DEC123 11.50 03/02/07 ABC123 10.50
What i need is a paramater query to be able to work to give me the total of the groups.. Whenever i try to join my Parameter query with my sum query it gets messed up..
heres the code... what am i doing wrong?.. What i want displayed after they input the date is the group by and sum total of the parameter query..
SELECT RawData_tbl.[Title 2], RawData_tbl.[Estimated Value], RawData_tbl.[Date In], RawData_tbl.Quote, RawData_tbl.GST, Sum(RawData_tbl.Invoice) AS SumOfInvoice FROM RawData_tbl GROUP BY RawData_tbl.[Title 2], RawData_tbl.[Estimated Value], RawData_tbl.[Date In], RawData_tbl.Quote, RawData_tbl.GST HAVING (((RawData_tbl.[Date In]) Between [Please Type the first day of the month] And [ Please insert the last day of the month])) ORDER BY RawData_tbl.[Title 2];
I am setting up a call log for an application. Once a message has been entered, I need to restrict access to the person who created it AND to managers (who have admin privelages to the database). Since the user who created a message needs to be able to go back in and edit it if necessary, I can NOT simply restrict access to the edit form to admins.
The command that opens this form looks like this so far:Code:If ((Me.[Transaction] = "Status Call") And _ (Me.[TransactionBy] = CurrentUser())) THEN DoCmd.OpenForm "frmEditMessage" ...Else MsgBox("Blah blah blah, etc etc.")End IfI need to add something to the initial If statement like this:Code:Or (CurrentUser.isMemberOfGroup("Admins"))but I don't know the correct Access syntax for it.
I am having problems developing a membership database - I have three main tables.
1. A table of 600 members of an organisation
2. A table of the subgroups these members may join, about 80 in total.
3. A table of the members of each group.
The members do not have a unique ID - complicated reason for this so I use a system assigned ID. Group ID does have a unique Id but I chose to use a system assigned ID.
Table 3 records effectively consists of just two fields, memberID and groupID. When I create a form and subform to enter these values all is well. But I cannot expect users to know these values, so I have been trying to create a subform that creates/lists/removes members from groups, using a Group main form with a member tabular subform with a surname search through a combobox. Groups have between 5 and 20 members.
e.g enter 'smit' in the combobox on the subform and a list of smiths is displayed together with the full name, from which the user selects the correct entry. At this point the record showing for instance, Paul Smith belongs to Group 17 is written to table 3. All sorts of issues arise, too many to document.
I am in the process of creating a training database that includes levels of proficiency with certain tasks for employees.
In one of my reports I would like to appropriately display with tasks the employee "Cannot Perform";"Can Perform with Assistance";"Can Perform Alone";"Trainer" (straight from the field list of the task). But I can't seem to get the hierarchy correct. Tried it in a PivotTable too as I thought similar to PTs in Excel you could get some kind of "count" of values. Couldn't make that happen either.
Each employee has a proficiency rating on about 20 different tasks. Proficiency input is controlled by a field list. I would like to structure this part of the report like so:
I was wondering if there was a way to view mdb file without the navigation pane and ribbon (for Access 2007). I know I've used an access database that someone else made and it was done in a kind of "user-only" style interface where all you saw was the forms and reports in a dialog box style. This kept the user from seeing any of the tables and queries and all the "under the hood" types of things.
