Search results

  1. E

    IsNull/Not IsNull usage in Iif Query headache

    Thanks Shoji - that worked! There was an extra "Iif" in the "UseCount" formula, but once I got rid of that, we were good to go!! :) Thanks too for the "Nz" tip. That was one of my "holes", which has now been plugged! :)
  2. E

    IsNull/Not IsNull usage in Iif Query headache

    Shoji - the problem with this appears to be that it returns a zero value as being the lowest - although strangely, it returned zero values even in calculations where the three fields had a value... :confused:
  3. E

    IsNull/Not IsNull usage in Iif Query headache

    OK, I'm sorry - I'm not understanding you. In my initial post I posted the formulae: PreFreezeCount: IIf(Not IsNull([RawStrawConc])<Not IsNull([PreFreezeConc]),[RawStrawConc],[PreFreezeConc]) PostThawCount: IIf([PostThawConc] Is Null,1,[PostThawConc]) UseCount...
  4. E

    IsNull/Not IsNull usage in Iif Query headache

    PreFreezeCount: 400 PostThawCount: 20 UseCount: 400 :banghead:
  5. E

    IsNull/Not IsNull usage in Iif Query headache

    Correct. Err... other than the "1" applied in the second formula, none. These are numbers derived from other entries made in the table (although I'm not sure if that answers what you were asking).
  6. E

    IsNull/Not IsNull usage in Iif Query headache

    Hello: I am a moderately capable Access user, however I am self-taught, so there are some holes in my knowledge which have a tendency to be filled when I run into a problem. Like now... :) I have a table in which I want to present in a report the lowest number of three fields. These fields are...
Back
Top Bottom