Recent content by plog

  1. P

    Nesting IIF Statement with functions that end in (field)

    Oh, this will be the time we just shut up about the right way and just give you what you want: https://www.access-programmers.co.uk/forums/threads/make-a-negative-number-a-0.333924/ https://www.access-programmers.co.uk/forums/threads/combining-iif-statements.333918/ This explanation won't...
  2. P

    DLookup on a SQL statement

    Agree with arnelgp, DLookup has no use in a SELECT query. But what are you trying to do? Let's suppose that Dlookup worked, what did you expect to happen in your SQL statement? I mean, the Dlookup is part of the SELECT, so it would have looked for a field named whatever your Dlookup...
  3. P

    Make a negative number a "0"

    More like a guidance counselor than teacher. Your teacher was MajP in the other thread. Check out post #20 there https://www.access-programmers.co.uk/forums/threads/combining-iif-statements.333918/#post-1960862
  4. P

    Solved Combining IIf Statements

    The saga continues: https://www.access-programmers.co.uk/forums/threads/make-a-negative-number-a-0.333924/
  5. P

    Make a negative number a "0"

    Ha ha, still not solved, still trying it the hard way: https://www.access-programmers.co.uk/forums/threads/combining-iif-statements.333918/ Even before this new wrinkle everyone advised a custom function. This additional logic now screams for one. Your logic is just too complex to cram into...
  6. P

    Solved Combining IIf Statements

    Still not detailed enough. You need to tell us every possibility, you've left out 2 cases still. What happens when single/married and gross income is above the respective upper limits you detailed above? Also are single/married the only options? No married filing separate? Are NULL values...
  7. P

    Solved Combining IIf Statements

    If that is correct, you only have 1 test necessary--the one that is not 0: Iif([MaritalStatus]='Single' AND [Salary]< [LowerBound], [Salary]-[LowerBound], 0) No nesting necessary.
  8. P

    Solved Combining IIf Statements

    I think you need to stop with code and start with English. As succinctly as you can tell us what you want to happen in each and every case. No code, just words.
  9. P

    Solved to return a ID value if criteria is met

    In post #8 you used the phrase 'worked perfectly' twice. Now, 6 hours later you are posting for more help. Did you solve your initial issue (the one from post #1) and we are looking at a new one or did you simply go 10 feet down a path you think is a solution to your initial issue and get stuck...
  10. P

    Solved to return a ID value if criteria is met

    I don't understand your expected results. But that's easy to fix. Just tell me what data you expect to end up with based on the data in your .pdf. No need for an explanation or any words, just give me the data you expect the query to return. What do the results look like? Again, no...
  11. P

    Solved to return a ID value if criteria is met

    Yes, but 'return' isn't the right verb or concept. Instead it would be more like identifying and using. To help specifically, we would need a better understanding of how your tables are laid out and what the ultimate aim is of identifying the ID. Are you opening a specific report? Are you...
  12. P

    DLookup Function Alternative

    Why are you moving data? In a referential database, you reference data, not move it. If you simply stored the Code value in your Purchase Order Details table you could then just link Purchase Order Details to Products and have all that data available. Why must it be moved?
  13. P

    Update records on a SQL Table

    Equivalent. 100 + (100 * .3) = 100 + 30 = 130 100 * 1.3 =130
  14. P

    Solved Creating a query with 1 table and 4 queries adds a new record

    Define "can't get it to work"?
  15. P

    Solved Creating a query with 1 table and 4 queries adds a new record

    First is advice you should learn in general, but not apply in this particular case: Divide, isolate and conquer. You've got 5 datasources in your query any of which could be the offending source with "duplicates". So, narrow it down to find out which one the culprit actually is. Start with...
Back
Top Bottom