Recent content by DDishShop

15 different tables. 15 different forms. Each form has several IIF's with Dlookups in text boxes (all are part lookups with cost). Want to run a single report on just the text boxes from all 15 different forms, not the fields. Built a multi query with only the fields with "New, Used, Warranty"...

Each form is asking for different information, they are all not doing the same thing, there is nothing wrong with the design. However, I am trying to combine all the information from each form into a single report. That's it, nothing more. What you are saying about the code could be useful in...

Just to clarify, each of the 15 forms the users fill out, is the same IIF()/Dlookup formulas in text boxes so the user has a running list of parts. When it came time to generate a report that combines all 15 forms, I hit a wall. That's when I figured I could do it all in a query, which...

I could not get the IIF formula to work in a Query as it does in a text box on a form. I tried all of the offered suggestions, but to no avail. It was eventually noted that some VBA does not work the same in a query as it does on a form. Taking that knowledge I came up with an alternate...

Dang Pat, harsh much? I have been learning all I can to write "code", but I am no genius as I am certain you must be. This whole post is about how something that works on a form is not working in a Query. So I had to make a fix. I created the form only for the direct purpose of putting in...

This was an "inherited" database, so there are many issues with it that I don't have the time (nor are my employers willing to let me spend the time) to fix everything, so I am more or less stuck with putting bandages on things just to get them up and functional again. The first thing I would...

I just don't understand how these formula's work just fine in a text box on a form, but not in the query that the form is based on. I did multiple compact and repairs but no change. It's only the IIF function that's giving me a headache!

Gasman: Yes, it is a lookup field with the options of New, Used, Warranty. So instead of "New", I tried 1. I tried the IIF using a non-lookup field and I get the same results - #Error. I even tried it with a checkbox value: FRRotor...

It's a string. The Dlookup portion works fine. I even tried a separate IIF: IIF([FRRotorsReplaced]="New","Good","Bad") If the value is "New", I get the #Error. If it's anything other than "New", I get "Bad".

Yes, in the column directly to the left of the expression. When I run the query the value for FRRotorsReplaced shows as "New". Just to clarify, if the result of the query is <> "New", then the result of the expression is 0. But if its "New", I get the #Error.

I have this formula that works on a form. It's in an unbound text box. IIf([FRRotorsReplaced]="New",DLookUp("[FrontRotorPart]","[BrakePartsGroup]","[AssetGroup]='" & [AssetGroup] & "'"),0) However, if I copy and paste this into the Field line of a new column in a Query, and give it a title...