Forms :: Limit Amount Of Data That Users Need To Input
May 23, 2014
We have a database where we are trying to limit the amount of data that users need to input.
We have a form, which contains order information. Where a customer has specific requirements, we add those requirements to a separate document review table MasterSpecification and DetailedSpecification.
When a customer has specific requirements, we can open the frmMasterSpecification and search for the document.
Assuming a review has been done the requirements will be shown on the subform Frmsubcoverage. I would like to be able to select the record source from this form and have the details entered into our order entry form.
Under the specification form there could be many sub coverage records depending on the type of item ordered to that specification.
I have created a switchboard 'front page' through which I hope for users to access the forms for inputting data.
Within this front page I have an 'enter' button - successfully created - everything.
However, I am unclear as to how you activate this, or any other button. I have linked it to the appropriate form and stated the action I want it to undertake, but nothing is happening.
What further instructions do I need to provide ...and where?!
How do I put an upper limit on the amount of time allowed in a date/time field?
For example - during a heart procedure a person is exposed to radiation, it will never be more than a total time of 10 minutes. I want to know how much, but I want data integrity so I don't want them to be able to enter more than 10 minutes.
I am creating an Action Item Database that will be located on a Sharepoint portal so multiple users can access and I'd like each user to have a login/ password to
1) keep unauthorized users out of the database and 2) limit what users can see.
This login/ security should ideally work so that user "Bob Smith" logs in with his assigned login/ password and he will only view/edit/ run reports for those Action Items that he has generated (field named "GeneratedBy") or have been assigned to complete ("ResponsibleLead") which are both fields in table "tbl_ActionItems". I can not tie the security levels to a users network login; this has to be security within the database. I don't necessarily need specific code at this point so much as I need a logical starting point for setting this up.
The Table1 holds data that is a request for a task.
ID, Request, Task_tms (the number of times the task is required to be done)
1, Make a cup of coffee,15
Table2 is my allocation of people to the tasks.
ID, Person, Task_done (the number of times this person has done the task)
1,Sally,10 1,Eddie,5
What I want to do is to limit the amounts of allocation in some way (ie in this case if I have already put 10 for Sally then I would be unable to put anymore than 5 when entering the amount for Eddie.
Additionally if I were to allocate all 15 to Sally then no additional people would be able to be allocated to this task (ID 1)
The two table are in datasheet format linked on a form.
How many users can an access database support? I'm setting up an app accross 3 workstations but each has multiple users. There may be as many as 1000 records a day entered. Can an access database handle this or do I need to switch to sql server?
- text box for user to enter EMPID, txtEMPID - LASTNAME
I would like to create a button to initiate a query to do the following:
- once the user enters a EMPID in the form, it will search in the TABLE under the EMPID field... - if the user enters an EMPID that is in the TABLE...display "Y" - if the user enters an EMPID that is NOT in the table...display "N" - a error message box needs to pop up if "Y" to alert the user that "the EMPID already exists and that duplicate entries are not allowed"
One of my main questions is how do I run a query based on the users input and search a table? would the following work in the query?
Best way to display "notes: field that gets updated/added to multiple times, in a form. (Access 2007)
I've got a DB to track information about product changes. Each month we have a meeting and discuss problem products. I'm concerned with a notes/comments section. Currently it is a memo field in the source table that can be added to, so the notes are cumulative. But we want to auto-add a date to each new entry (in case the person inputting the data forgets, and so that notes can be sorted by order on a report).
There may be many comments on a certain product or there may be none. Sometimes the note may be very long, other notes on the same product may be very short. I created a new table with a one-to-many relationship to case ID (to link it to the main form), auto-populate a date field, and field for notes in order to link multiple notes to each case (and of course an autonumber PK).
I can put the subform in the original form, but then the note field will be the same size for every note, though notes are not all uniform in size/length, and it ends up taking up a LOT of room on the main form. So I created a button to click to open the subform, but it brings up all records for all cases, not just the currently selected case. Again, have the problem of one uniform field size for all notes, regardless of size/length.
Then I considered a report to view past history (field size can shrink or grow as needed) then a button on the report that opens a form for data entry/entry of new note. But again the report displays all records for all cases, not just the currently selected case.
My DVD library database I have a memo field which has the description of the movies.
In some cases, like my tv show records, I have a lot of data because of the episodes and episode descriptions.
I'm currently displaying this data using a split form with the datasheet on the left
I must use a small font in the memo field in order to display all data.
I could use a larger font and simply scroll but I'm looking for an alternative.
I've even thought of creating a hyperlink filed and point to the movie on IMDB's web site. But when I click the link nothing happens even though I copied and pasted the link into the field.
I have a small database for doing some tracking and some reporting. I want to be able to allow everyone to view the data and also to print reports. However, I also need to limit who is able to enter data into this application.
I don't want to build a login form for the application...I want to be able to limit users based on their Windows Login name, which I would have in a table. The first thing I would do is compare their Windows login name against the table, and then put in code such as "If table name = suchandsuch then you can't do suchandsuch, but if tablename = blahblah then you can do something."
Is something like this doable? If so, how might I go about getting started with this train of thought?
Thanks to any and all who respond..... I appreciate your time and knowledge!!
I have a voting application that need to limit users to only be able to login once to vote.Firstly how do you record in a table when a user login and at the login form how do you check to see if the user have logged in previously.
I have a login form with a username and password fields that work perfectly.
I have a number of smaller queries that I want to join together to create a super query to display on a report. It works fine when I have a dozen queries joined, but as soon as I add any more, the query takes at least 10 minutes to run (although it eventually works). Is there a limit to the number of queries I can include in a query or is there some other underlying problem? NOTE : the smaller queries only contain half a dozen records with totals.
I am using Access 2007. My boss has given me a project to create a tool for our team. I'm done with most part of the project, but for the last part I want editing and updating of database restricted to a few members of our team. However others can access the database and run queries etc. through buttons on a form.
I went about creating a login form for users to get access to the database and in turn created a table with fields UserID, UserName, UserPW and a yes/no field titled IsAdmin. For those who would be limited access would log in as 'Other' user and same as password. I am then using the code to determine if the user should be treated as admin or not by looking up the IsAdmin field in the table. Following is what I have so far, but it needs correction some places and I can't figure where:
Private Sub cmdLogin_Click() Dim xxAdmin As String 'Check to see if data is entered into the UserName combo box If IsNull(Me.cboUser) Or Me.cboUser = "" Then MsgBox "You must enter a User Name.", vbOKOnly, "Required Data"
I am trying to uses a inputbox. I need it to end the script if cancel is hit, but the value from the input box can be zero? So cant filter it that way.
Also
Does the SQL command LIMIT work in access and is it possible to number row in order?
I have a split design form, where user can select on any row and column of the spreadsheet view of the form and edit the data. Now, I want to write a code to limit the data addition(Row addition) to a certain number. But I still want to be able to edit the previous records added to the form.
I used Me.AllowAdditions = False, but when I want to select the previous records, it gives error:"You cannot go to specified record".
I have a form with four combo boxes on it, the four boxes all open the same form and return a record based on the selection from a different column from the same query.
To make it work smoothly I think I need to make it so it is only possible to enter data in one combo box at a time. I could also do with some error handling.
I have a form I created in the past that auto-fills some of its fields based on the user's selection of a record from a combo box linked to another table. The form has been working perfectly however I recently tried to add a couple of more fields to the form that need to be autofilled. I added the new fields to the source table and added columns to the combobox that should allow my VB code to fill those boxes. However only one of the new fields is filling correctly. After trying a few different things I notice that the problem seems to be with whatever data field becomes the 21st column in the combobox. Is there some sort of limit on the number of columns contained in the data source for such a box?
I an trying to create a data entry form (IndividualsEntryFm) to input data for fields such as (First Name),(Birthdate) etc., these to be saved to the (IndividualsTbl)
I also have another table (NamesTbl) which has family names etc. The two tables are linked by a (MainID) field. I want a combo box on the individualsEntryFm so that I can select the family name. Then I wish the empty fields for the IndividualsTbl to be available to enter data.When I press the save button I then want this data saved, together with the MainID from the combo box to the IndividualsTbl.
I have set the IndividualsTbl with a (PersonID) field as an auto number each individual therefore has a unique PersonID but may well share the MainID. I'm trying to link many people to the same address.
My database is tracking Job/Project information. The users must assign the Job Contacts which can be both internal and external (ie: Contracts is a Client Contact, while Engineer is an Internal position)..
tblContactTypes which defines each of the 10 types of job contacts. fldTypeID: fldTitle fldClient fldInternal 1 Contracts True False 2 Engineer False True 3 Other True True
The Job Specific data is stored in tblJob_Contacts
fldJobID (PrimaryKey) fldTypeID (from tblContactTypes) fldEEID for Internal Contacts (from tblEE) fldContactID for External Contacts (from tblClientContacts)
My question is this...How can I force the user to enter the Contact information for Contact Types 1,2,3, and 4 while leaving the remaining contacts types as optional?
I would like a form with combo boxes for the first four Contact Types which must be assigned for every job and then a continuous subform where the user can assign the remaining contact types if needed.
Initially, I planned to store the first four Contact Types as separate fields in the main table (tblJob) - however, distribution lists are needed and it makes more sense for all the contact information to be stored in the same table.
I am trying to set up a password on a for different users to have to enter pins to enter data. When a user selects his/her name from the combo box the next field will be something like pin. When they enter the corresponding pin this will allow them to edit and start or continue (if they left) fill out the rest of this form.
The reason being this way is that if one of them goes back to a previous record done by another user (which I want them to be able to view) they can view it but cannot edit it because they do not have the users pin (or password). Is this able to be done, only allowed to edit or create a new record if you enter your pin every time.
I am building a very comprehensive Membership Management Database with extremely useful facilities initiated by some 20 or 25 Queries..
The database includes 5 Tables which store data relevant to members, another which stores details of Interest Groups and a 3rd which stores which members are affiliated to which Group or Groups.
Currently the database is accessible only by a very limited number of persons and data can be entered/edited by only one person. The database, using Access 2010, is maintained on a desktop computer and synchronized to a copy on a Cloud.
My requirement is to permit some 50 Group Leaders to input/edit data on a Password protected Group Members Form such that that is the only element of the database that they can access. The Forms would have only 2 fields from which the user would select entries from drop down lists.
My query is ; is such a procedure feasible in principle and would I be correct in assuming that the user would require to have available a copy of Access.
I have One table(and designed form from it) in which i have recording the daily transactions(it is like a daily book). Daily transactions took place like Purchase of items of Amount 45, sale=70, sold on account=100 etc.
What problem i am facing is: I would like to Add Cash In Hand amount and would like to show it on my form. When day end I would like to move remaining cash In Hand on separate column of that date. The next day i would like to take the previous Remaining Cash in Hand as Cash In Hand at Start for next date and so on.
I have a form, and on the form there is a Provider Rate which is a combo box, if the user select a zero rate, then it has the description please enter manual rate in box below. There is another box which the user can enter a manual rate.
how I can limit entry into these boxes, as currently a user can select a rate in the provider rate box and still enter something into the manual rate box. I want it so that if a rate other than zero has been selected in the provider rate box, then they can't enter anything into the manual rate cell.
I am trying to make a report in which I can see the amount of money that I have to pay weekly to an employee. To explain myself clearer, I have different rates for each employee. For example:
NameNormalPayRateVacationPayRateSickPayRateOvertimePayRateStandbyPayRate John Smith$15$10$15$30$8 Ken Jonson$10$8$10$20$8
I am doing this in a query. So what I want to be able to do is, for example, take 4 hours that the employee worked at NormalPayRate and multiply it. But if tomorrow the employee worked at a different rate, for example 3 hours overtime, I want those 3 hours multiplied by OvertimePayRate.
The way I saw it on my Google researches, is that they have only one rate and the amount will be [SumOfHours]*[Rate]. But how can I tell my query to skip, for example, one rate because the employee didn't work at that rate that day. So I can have different amount for the different rates.
By the way, entering the information I can divide at what rate the employee worked x day. So if the employee work 6 hours at regular, and later on 4 hours at standby, I have those information separated in my table.
Results that I am getting: I can easily get the amount in money multiplying the whole hours by a rate, so my result in my report will be multiplied by the same rate.
When I learnt to use vba in excel (to basic level) I was always advised in a userform to validate data at end of record input i.e. when pressing enter and next. Is this true also with access or should i be putting validation rules at the afterupdate stage of a particular control?
