Ok I have heard many times that you should never save a calculated field in a table. I know this is breaking the rules but can someone tell me how to save a specific combo value change to a table? and avoid all the rest?
Here is my problem, I was asked to have a combo box that has 5 choices and when the default is changed to another choice, I must have the date saved for reference. But the date is only supposed to be saved when a specific option in the box is choosen. Such as
Default: basketball
was changed to football
I can do a timestamp but don't know how to change it when a specific option is selected. It just changes when it is updated , even when I change it to baseball
Im actually saving it but can't annoy the other options...
I want to take a report which covers sales figures and e-mail to those people that have had sales in the period. I only want each person to get just their records, not the whole report. Any ideas how I can do it automatically, starting with a query of records or a report ? ?
I know how mto e-mail a standard report using a macro !!
The work hours for a person is entered once a week, at the end of the week. The person's SkillID can change but not in the same week. For ex a person scheduled as a Welder has to work as Welder for that week.
So, I need to find now all the PersonIDs with more than one SkillID in a week and flag them as errors.
Pls check the attached image. The first entry with EntryDate as "06-May-05" and Person_Code as "MK0259" repeating with 3 different Skill Codes. Then this is a problem which I want to hight light. Hope I explained clearly.
I have a report - I have a agent header and code header.
It should look like this:
Jeff Moenning Agent Header 1-Active Code Header Report Details
For some reason the first page just has Jeff Moenning and nothing else - after that the pages are correct. They are breaking when the agent changes and also when the codes change within the agents.
and so on and so forth. Is there a way Acess can break the fields out? I want 1 field with CAN, 1 field with the year, 1 field with US, and 1 field with the number (4 different fields broken by the hyphen).
I can do text to column in excel before I import, but just wondering if it can be done in Access. Thanks in advance, guys...
I am attempting to create a report that breaks down a field of 'ClaimID' numbers into groups of x. In the sample report below x = 12 and the report will apportion the first 12 'ClaimID's to the first page and textboxes with extra large fonts will signify the start and end of 'ClaimID' numbers for that page. These sheets are used for sorting and pulling guides at our local Xmas project and x will vary depending on the size of the facility we're using. http://i35.photobucket.com/albums/d186/HoodRiverDude/SortReport.gif I believe I can attain my goal if I were able to create a query which broke down the field 'ClaimID' into multiple fields based on x. The sample below represents this breakdown creating multiple records with x, 4 and 5, amount of fields. http://i35.photobucket.com/albums/d186/HoodRiverDude/SortReport2.gif Does anyone know how I can create this query, or perhaps suggest another way to create this report using the existing 'ClaimID' data.
Let's say that a table has been broken in two and I'd like to rejoin them with a query. Let's say 100 records in table1, 20 records in table 2. Here's a random example, I just made the names up off the top of my head:
PersonTable (100 records) Person # (unique key) Name Address
SpouseTable (20 records) Person # (lookup wizard to Table1, cascading edit/delete relationship, 1 to 1) WeightOfSpouse HeightOfSpouse
Many people aren't "married" and so have no corresponding value in the Spouse table. If I do an inner join on the two tables, on Person#, then it will cut the total # or returned records in the query to 20, to match the total in SpouseTable. Essentially, I want to append the results of SpouseTable to the end of the corresponding rows in PersonTable.
I have a report in which there is a subreport that prints towards the bottom of the page. I know that I can use grouping to have the subreport print on the next page if the entire subreport cannot print on the current page. However, I want to have the break occur not for the section as a whole but between records. Let me illustrate this.
All sorts of other stuff prints at the top. At the bottom, I have a subreport which today prints the following on the first page and breaks the last record in two printing the second line on the next page.
First Page of the Report: __________________________________________________ _______________ Doctor's Full Name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Doctor's Location: XXXXXXXXXXXX
Doctor's Full Name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Doctor's Location: XXXXXXXXXXXX
Doctor's Full Name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX __________________________________________________ _______________ Second Page of the Report: __________________________________________________ _______________ Doctor's Location: XXXXXXXXXXXX __________________________________________________ _______________
What I would like to do is the following:
First Page of the Report: __________________________________________________ _______________ Doctor's Full Name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Doctor's Location: XXXXXXXXXXXX
Doctor's Full Name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Doctor's Location: XXXXXXXXXXXX __________________________________________________ _______________ Second Page of the Report: __________________________________________________ _______________ Doctor's Full Name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Doctor's Location: XXXXXXXXXXXX __________________________________________________ _______________
Is it possible to specify that if a complete record within a subreport cannot be printed on the same page to break to the next page without having the whole subreport break to the next page?
I have a date field on one of my forms that gets populated automatically when a new record is created. I also have a subform on the form that lists the tasks that still need to be accomplished this month. Some problems have popped up as people got new computers with new versions of Access:
Access 2002(10.6501.6825) SP3 - No problems. Access 2002(10.6771.6817) SP3 - The Date field isn't recognised on a new record (#Name?), but it's fine on the old records (displays date). Access 2002(10.6771.6825) SP3 - The reminder subform is blank (white), as if it doesn't exist, but the date field works fine.
Any ideas why this might be/how to fix?
Thanks! This is really frustrating. If it didn't work for anyone, I would find a way to fix it, but because it works for some people, I don't know what to fix...
I have a situation where i need to import a table in Access which is in Excel, After importing i need to know how can i break it up differently keeping relation of FK and PK intact: E.g.
Excel Sheet:
Name Biz ID Biz Name Address1 Address 2 Address 3 OrderNo Order Date
Person Record ID(PK) Name Biz ID Biz Name Address 1 ....
I am trying to figure out how to take a table of timestamps and activity duration and break it into intervals, where it groups the duration into the time spent in each 15 minute interval. I have included a sample of the data and output. Is there any way to pull this in Access (or SQL)?
Raw Data EmployeeActivityTimeStampStartTimeStampEndTotalDuration Doe,JohnSomeActivity12/16/13 9:06:02 AM12/16/13 9:57:14 AM0:51:12 Smith,JaneOtherActivity12/16/13 9:22:15 AM12/16/13 10:06:55 AM0:44:40
Query to break out the total duration time in to the 15 minute interval it fell into
I want to base my validation rule on the input mask, so I can use the validation message if people are having problems entering data in the field.
I have no idea how to do this. I tried to copy and paste the mask into the validation rule property but that obviously did not work.
PS...I dont know if this will help, but what actually goes in the field is the month in a number format, the year in a number format, user initials with another number behind it. So like 01-05-CG1 is what needs to go in the field.
How do I create a validation rule that instructs people to enter data in this format?
Hey guys, I'm very new to access. I have version 2003.
I want to create a validation rule, that will basically only let me enter values into the table between a certain range:
i.e. When were you born? The only possible dates can be 1950-2006.....so how can I set this up so that when someone is entering this data, they cannot enter, say, 1950? Thanks for any help!
I need to make sure that a user doesn't enter anything but a number in a text box. It is on frmDownTime and the name of the text box is dtDownTime. How would I go about entering this? Using the Properties, Validation??
I've tried using validation rules in a table. Like the rule i set for a field was <4. I assumed this meant all data entered has to be less than 4 digits. Happy. Then i test using a six-digit figure: 245545. Its still happy!!!!! :mad: No error. Am i missing the concept??? :confused: Furthermore. After setting the rule, my table and query stop being linked... If i load an entry through query, table doesn't update its info..... This was not the case before. What am i not doing??? or maybe: What am i doing wrong??? :confused: I'm hopeless at this program!!!!!!! Any help/insight would be HIGHLY appreciated.
I have a question about creating tables in Access with an SQL query (or VBA, I guess, if that's not possible, though my example below is SQL). Specifically, I'd like to know how one adds validation rules programmatically. For some reason, I can't seem to find this information.
For instance, for simplicity's sake, let's say I'd like to create a table (table1) with a single variable (varx), a long integer, and I'd like the validation rule to be "<5 or >10".
I know how to do everything except add the validation rule in. So what alterations would I make to this to add it?
I'm designing a table in design mode using Access 2003. What I want to do is limit a field named "ClassLevel" to only accept the following values: JR, SR, 2BA, GM. I tried the code Like "JR". That seems to work for just JR. But what I need is all 4 to be set. I then tried Like "JR, SR, 2BA, GM" That doesn't work. Please let me know how I can do this. Thanks.
Question I am looking at some annoying Access database for a charity and got stuck on trying to make something work that they believe used to
Two Tables
Venues pK Venue ID Venue Name Venue Capacity
Booking Venue Name Addr1 Addr2 Addr3 Ect
They have a query call capacity check which does the following Count Occurrences of Venues then takes this away from venue capacity
Essentially they have a standard access form of the Booking table with a drop down box and want it to only validate if seats are still free at a venue eg if the current count for venue is less than the venue capacity.
I would love to perform this validation rule on the table
Is there a listing anywhere online for common regular expressions for validations rules? In other words, is there something that shows how to construct validation rules for things like phone numbers, addresses, postal/zip codes, serial numbers, math equations, etc. Two in particular that I'm looking for are phone numbers and postal/zip codes. Every time I try to wrap my head around the formula for a phone number (with area codes, an optional 1 in the begining, making sure no leading zeroes, making brackets around area codes optional, etc.) I only get a headache :mad: . I'll get it eventually, but a quick reference in the mean time and for future use would be very helpful.
I'm trying to append data into a table, but getting 11 records rejected on validation rule violations, but i have none set. can anyone explain why this might be?
I am as new to MS Access as you can possibly get so please forgive such a simple question. I created a table in Design View. On one of the fields in the table I want to restrict the values that the user is allowed to enter to either a capital Y or a capital N so I created the following validation rule in design view:
=UCase("Y") Or UCase("N")
No matter what I do, the data sheet view allows me to enter a lower case Y or a lower case n. How can I make sure that this field only accepts a capital y or a capital N.
Hi, I have the following code which adds text and number fields as required, but I need to add validation rules and text as well within this code, but have no idea how to do this and have not found much help on the net.any help appreciated...tan
Dim db As Database Dim tbl As TableDef Dim fld As DAO.Field
Set db = CurrentDb() Set tbl = db.TableDefs("4WeeksFollowUp")
Set fld = tbl.CreateField("text", dbText, 30) 'for text - 30 is field length Set fld = tbl.CreateField("CO3", dbLong) 'for number tbl.Fields.Append fld
hello, i am super duper new... and am working on a school assignment for weeks! its due tomorrow but i cant get this one rule to work... please help if you can!! Basically I am trying to add a validation rule to a field refering to a different field in a different table. Both fields are Date/Time type I am new.. and not as advanced as some of you.... so maybe walk me through it?? i have spend many hours trying to figure it out~ thanks
I have a field that looks up the JobType using a LookUp Combobox from another table where these records for JobType will never change.
I want the user to only be able to select from the Combobox for the job type they want and be able to type the beggining of the job type so that the desired job will pop up. Now, i need the field to not be able to accept any other data than what is in the LookUp, so that they cannot enter false values. Duplicates of jobtypes are possible so a primary key cant be used.
I'm using a simple input mask via the wizard for a date of birth field in a table, but the table is accepting entirely invalid dates such as 32/12/2005. When I tried inputing something like this in the wizard it says invalid input, so why is it valid in the table? Should I set validation rules? I tried this: >31/12/2004 and set the validation text to "Invalid data" i.e. limiting input to less than 31/12/2004... but it still didn't work.
