I have a query which based on some fields on a form should display a set of records. In case when the user doesn't specify anything in the combobox on the form (value=NULL) I want the query to display all the records (like "*"). For some reason when i put the following in the criteria of the query it returns 0 records instead of displaying all:
IIf(IsNull([Forms]![frmClassReport].[ClassName]),(([tblClassesOffered].[Course]) Like "*"),[Forms]![frmClassReport].[ClassName])
I tried: IIf(IsNull([Forms]![frmClassReport].[ClassName]),"class_name",[Forms]![frmClassReport].[ClassName])
... and that works properly. I tried several scenarios and pretty much narrowed the problem down to the use of "LIKE" which when used as specified in the first SQL statement doesn't return any records. What am I doing wrong?
I have a query that returns hours of vacation time taken for each specfic day of the year. But if no time is taken on for example Jan. 19th, that date do not show up in the query. I am wondering is it possible to return all 365 days and display a zero,if nothing is booked for that day. Attached is the db.
I need the following to display a zero if a null value is returned:
SELECT tdsIndivData.dsReportID, Count(tdsIndivData.StaffID) AS CountOfStaffID FROM tdsReportData INNER JOIN tdsIndivData ON tdsReportData.dsReportID = tdsIndivData.dsReportID WHERE (((tdsIndivData.Availability)="75% Availability")) GROUP BY tdsIndivData.dsReportID;
tblDrawingRegister - stores information about construction drawings tblDrawing Revisions - each drawing in tblDrawingRegister has one or more revision or version tblVendorDrawingList - this table has a list of drawings numbers that correspond to the drawings in tblDrawingRegister.
The drawing numbers from the vendor table as provided as an 'extra' as some people are more familiar with this numbering system.
Now the issue is that there is a one-to-many relationship between tblDrawingRegister and tblVendorDrawingList. In the screenshot I've attached there are 14 drawing numbers that correspond to one drawing number in tblDrawingRegister. (This is because the main supplier has packaged 14 drawings as one with just one drawing number). When this is the case I want to display the drawing title from the Vendor table. Otherwise if should just show the title from tblDrawingRegister.
I have tried using Dlookup to show the title from the vendor table when there are dublicates in the vendor table. It didn't work and I think this would be really slow. I've tried a few other things too but to no avail.
I really hope that this is clear. I've attached screenshots of the query too.
Days on Hold: calcworkdays([on hold date],[off hold date])-1
Now i have a module thingy set up (calcworkdays) which works out working days. What this expression does, when theres an on hold date and an off hold date is work out how many working days something is on hold.
Now, problem is, not always is something on hold, therefore fields are often blank and then i get a result in query that says "#Error", but i want to use the answer to this expression in another formula, but when error is displayed it makes the other query show error too.
What I want is some sort of If statement or similar so that if no results exist to display "0". Can anyone tell me how to add this in?
I'm a total Access Noob, it took me forever to work out this working days thing (damn access for not being as simple as excel!)
I think my problem might lie in the way the function has been written. I think i might have to modify this to show "0", rather than "error"
This is what ive got in the function.
Public Function calcWorkDays(dteStart As Date, dteEnd As Date) As Long Dim i As Long 'day counter Dim dteCurDay As Date 'set i = 1 if you want the first date to count as a full day 'or i = 0 if you do not want the first day to count as a full day
i = 0 dteCurDay = dteStart Do Until dteCurDay >= dteEnd 'check date against holiday table If 0 = DCount("[HolidayDate]", "tblHolidays", "[HolidayDate] = #" & dteCurDay & "#") Then 'continue checking for weekdays If Weekday(dteCurDay, vbSunday) <> vbSunday And _ Weekday(dteCurDay, vbSunday) <> vbSaturday Then i = i + 1 End If End If dteCurDay = DateAdd("d", 1, dteCurDay) Loop calcWorkDays = i End Function
I have a field called PRICE and obviously it is a NUMERIC field as it need to perform calculations such as calculating Total Quantity * Price etc. At the moment the PRICE is inputted manually by the User on a Form and when it has no Price it is simple left blank.
What I wish to include is that on the REPORT when the field is empty it writes the text FOC instead of leaving it empty.
Can you please anyone suggest a way of doing this.
It might be an easy one but I just wasted the past hour deciphering through my code in order to solve the run-time error '94' that I'm getting when trying to execute the following code:
Code: Private Sub cmdUpdateDates_Click() '################################### 'This sub aims at combining the timesheet date and the start and end time into the fields [Start Time] and [End Time]. '################################### Dim intCounter As Integer intCounter = 0 Dim rs As ADODB.Recordset
A bit of a weird one, I've got a query and the criteria for showing records is that one particular field is null. However the query is showing records with the values in the field chosen for the Is Null.
Not sure why this is happening, has anyone come across this problem before?
I am having problems with setting up a set of combo boxes.
What I am trying to do is if combo Productline is empty then in combo PartNumber would show all products but if combo Productline has a value selected then in the combo partnumber would only be able to select the partnumbers in that productline.
Hi, I have some problem with assigmnet with date and string variable. what i wana do is get data from Forms textboxes into variable and then by insert query send to history table.
the problem occurs when there is blank textbox its says invalid use of null.
I have a query where data is first sorted by user input; first field's criteria: [fieldname], then by another field's criteria: Is Null.
I know there are records containing null values in the second field, as I have run a select query with the criteria: Like "*", to make sure they are null, and not zero-length-strings.
I have created a data base over the last few months I just kept adding information in the fields that I created but now have a problem I have the sections in a drop down menus of which access will let me ad info but when I com to save I get this message "Index or primary key cannot contain a null value"
Access will not let me save any added info in any field I have tried all the ways that I know to get round this problem to no avail it is most properly some think silly but I am desperate now as I have worked hard on this project.
I am using Access to connect to a sybase (symposium) database... I pull records depending on what state the record was pegged.... This is based apon a user inpuyting a code on a telephone. Of the user puts a number that does not reprsent any of our set codes it will show the code feild as blank or null. I need to make this blank feild something representable as furhter down my querys it removes these blanks or nulls. I would like the blank field to be shown as "Bad Code"
Any help would be great...
p.s I have used iif and as and like and nothing is working..
I would like to know if is any way to inverse the following code: This: if isnull (txt1) then 'recognise if the box is empty to something like this: if isNotNull (txt1) then 'recognise if the box is not empty
In response to: http://www.access-programmers.co.uk/forums/showthread.php?t=131593
I personally believe 'NULL' should be banned as a possibility entirely. :eek: It has been pounded into my head that 'NULL' is not the same as 'EMPTY' or 'ZERO'; and that it literally means 'NOT KNOWN'. Now consider a contact database that has a field for lets say Apt# or Street Direction such as N or S or ?? as an example. There are many, many instances where these fields would be left blank or empy: NULL | NOT KNOWN. When in fact the situation is known: the object has no such attribute; and in query or some other form of program logic the venerable NZ(subject, response) function may be used which would replace the NULL with a value. Or program logic and or error trapping would be used to handle such occasions. Which is an absurd waste of time and talent IMHO.
Therefore, if there is no applicable attribute to enter (something known) why not say so with 'N/A'? Else what we are saying by using 'NULL' is that we are building a dataset containing data that cannot be known. Kind of like saying
In response to: http://www.access-programmers.co.uk/forums/showthread.php?t=131593
I personally believe 'NULL' should be banned as a possibility entirely. :eek: It has been pounded into my head that 'NULL' is not the same as 'EMPTY' or 'ZERO'; and that it literally means 'NOT KNOWN'. Now consider a contact database that has a field for lets say Apt# or Street Direction such as N or S or ?? as an example. There are many, many instances where these fields would be left blank or empy: NULL | NOT KNOWN. When in fact the situation is known: the object has no such attribute; and in query or some other form of program logic the venerable NZ(subject, response) function may be used which would replace the NULL with a value. Or program logic and or error trapping would be used to handle such occasions. Which is an absurd waste of time and talent IMHO.
Therefore, if there is no applicable attribute to enter (something known) why not say so with 'N/A'? Else what we are saying by using 'NULL' is that we are building a dataset containing data that cannot be known. Kind of like explaining:
how do I set an entire colum to not accept nulls. example I have a colum that will be checkboxes. I want all the checkboxes to be in the unchecked state.
When filtering by form I suddenly get the words: Is Null / Is Not Null appearing in the drop down menu of all fields. I can then no longer filter at all? This is carried over to filter by form too!
When I export, or cut and paste the records into my backup database (filters working ok before I do!) the same thing happens!
I new to access and need some help, here is my problem. I have a query that gives data to a table, the only problem is that there is blank fields in the query and from what I read that is not a good thing when doing calculations. Here is the formula that I am using in the query DaystoCloseNonQSF: IIf([QSFNonQSF]<>"qsf",CalcWorkdays([DateReceived],[DateCompleted]),"") Then I need to get the average of the days that this formula returns, since there is blank fields it won’t. I hope that this makes sense.
I am trying to create a query whereby it will only show only those records when the x field is null. I also need a separate query to do the opposite, i.e. to show only those records which have x field not null.
How can I do this?
I know I need a statement on the x field but don't know what it is?
I'm trying to get this to work but is having a few problems. Hope someone can help.
SELECT * FROM MTL_Log WHERE (((MTL_Log.AccountingName) Is Null) AND ((MTL_Log.AccountingID) Is Null) AND ((MTL_Log.AccountingDate) Is Null));
I have the above right now. But it's not working right. I need the statement to pull all the records where AccountingName and AccountingID and AccountingDate are null and also if any of the field is null. Right now, if at least one of the field is filled in, the do not show in my report.
Any ideas on how to get this to where if any of the field is null then the record will show?
I have a table with a name field and five other fields. I want to create a query where it would tell me if the fields have anything in them or not. I created a query and put in the criteria "is null" and I got nothing in return. Then I put "is null" in the first criteria field and "is null" in the remaining field, but on the "or" criteria line. It worked, but I'm missing records because they dont add up between the number of records in the table and between the nulls and not nulls. Can anyone tell me why and what I am doing wrong please?
Is there a query that first finds out whether a field is null that then goes in to more If functions?
This is what I have at the moment:
If mixed = "town centre" then mixed_ratio = "25%" else If mixed = "employment" then mixed_ratio = "100%" else mixed_ratio = "75%" end if end if
this code works fine, but if delete what is in the mixed field, it automatically places 75% in the mixed_ratio field, which is not what I want. What I want is for the mixed_ratio field to be null if the mixed field is null.
I have tried putting an If Function at the beginning that says If mixed = Not Null then do this and this etc etc and finish it with mixed_ratio = Null but it doesn't seem to work and also stops the rest of the If Functions happening.
