Recent content by Agnostiker

Hi Chris! ...and that's the reason one must 'invent' two new 'AND' and 'OR' operators? http://support.microsoft.com/?id=817250 Another instructive article I found here http://www.mvps.org/vb/index2.html?tips/truth.htm Ciao Willi

Dear members, having had a very instructive and enlithening journey on the marvelous land of the disregarded and frequently even calumniated IIF function (Thanks to all) I would like to wash out the ash from my hair and return to the origin starting point throwing my last dump question into the...

Chris, fortunately having my 12th cup I think I could follow your explanations. And as I followed it fell like scales just from my hairs: what a stupid, simpletonary and dumpfpfeifentrotteliger* Kraut I am! Apart from having given today two or three wrong and absolutly foolish advices, I did...

Ops, my idea was really stupid, sorry! :o I didn't knew before. Thanks Pat! Willi

Thanks for your confession, Pat! So I'am relieved... :) And I think, we all are in the same line: IN GENERAL DON'T! That's right? Regards Willi

Mille grazie, Wayne! But to explain that 'mysterious' behavior of 'IIf' (see Posting #10) we need to have a construction like this I think: IIf(A > B, C, D) where 'C' or 'D' could be a 'division-by-zero-expression' f.e. So I suppose, 'C' and 'D' will be loaded in registers also in the...

Think it's dependend from what is in foreground... :cool: Willi

Hi Chazer, if it's not allowed to change the membership numbers, you could create this new table with an autoincrement field and then add empty records (they have only this memb. number), for example, if you have numbers in the range [0...2000] you have to add 2000 new records. Then you'll...

...and now toooo slow! :D

Ops, ok, sorry! :o Once again: DoCmd.OpenForm "YourForm", acDesign Forms!YourForm.OldName.Name = "NewName" DoCmd.Close acForm, "YourForm", acSaveYes Do we got it now? Willi

Like this? DoCmd.Rename "NewName", acForm, "OldName" Regards Willi

Sorry, no. :o This is not I'am talking about. As shown before (see the instructive Posting #10 from Pat Hartman) there must be a difference between an IIf statement and its 'equal' If-Else solution. So my question is how the compiler is translating this IIf statement in machine code ...

In the past I avoided the IIf-statement, but in case of simple 'display switch' for exampel like lblXYZ.Caption = IIf(IsNull(strQ), "Kraut", "Kindergarten") I learned to like AND use AND read it, saving space. (Thanks Chris recalling the origin ;) ) So I think too it's dependend from how...

Try If rs.NoMatch Then .... Friendly regards Agnostiker

...so I'm appeased! :)