Search results

Oh yeah, I'd forgotten about ParamArray. That is cleaner, but it's still not working - I'm still not getting a ref to the original control. When I put in a breakpoint and step the code, I have the value of the checkbox, but when I change the value of the Ctls() element, nothing happens to the...

I have a set of routines that do various things to controls - enable, visible, lock and so on. It is faster, cleaner and prevents screen flickering when setting a property that is already set. Here is one such routine: Public Sub gbl_CtlsAbled(ByRef arr As Variant, ByVal Stav As Boolean) Dim i&...

Fine, except that she wasn't "right on the technical aspect all along". She was wrong on the technical part. If you agree with her, then you're wrong as well. She accused me of all sorts of crap I didn't say, and in #20, all I did was answer HER insults. Yeah, I overdid it.

You're not - I was. I let myself get provoked by foolishness when I should have just ignored it. Sorry to everyone who got exposed to that.

Yeah, sorry about that. I get irked when someone thinks that a helpful contribution is to ignore my question and tell me I am doing it all wrong. And then continue to harp on it when I tell them I know what I want and am doing it that way on purpose. But you're right - I overreacted. I should...

I don't know the value when I'm doing the lookup. I feed in the ID and expect to get back the value. Sometimes that value is blank, other times it's text. But I focused on the blanks because that is what is misbehaving. When the value is a non-empty text string, DLookup returns it correctly...

Yes, MajP pointed that out to me in one of the first responses in this thread.

Yes, those are the results I also get when playing with this. All seems to work properly, except for actually returning the contents of a ZLS. Those it converts to a null.

Maybe you have to sacrifice an iPad or iPhone. As to your examples, I have no idea what is in your table, so I can't comment on the numbers you get. But the search criteria works, as far as I can tell, so if you have 972 records with a blank in that field, and 217 records with something other...

Hm. If both ZLS and vbNullChar return Null, and DMin and DMax do so as well, that would seem to point more to a conscious choice rather than a coding error. But I can't imagine the justification for intentionally designing such behavior. Do you have any idea?

The real one does have such a default value. This was just an example I knocked together to answer DBGuy's question. The blanks in my real DB are strictly created by code, though, under a particular set of circumstances, never imported or left to the user, so a default value isn't really...

Yes, it does, and I am convinced it should not. Didn't know min and max also did that, though - thanks.

It didn't take too long. It was in a simple search routine populating some visuals on a form. When they didn't populate correctly, I started digging into the code, and soon enough, I got to where I typed ?DLookup(blah) into the immediate window, and got Null. I then started poking around some...

Yes, DLookup does behave differently from DAO, and I believe it is simply wrong. I cannot imagine any justification for a search function returning data that does not exist.

I can. The point of the design I selected was that I didn't have to. The incorrect response of the DLookup function means that I now DO have to again, or figure out some other way to retrieve my non-null empty string. When I have an empty string, I expect the DLookup function to get it for me...

Curious, though - what do you mean by normal behavior? If you mean that DLookup is known to do this, then yes. If you mean that is is supposed to be doing this, what do you base that on? It does not seem to me that changing found data is proper behavior for any code.

Thank you, but I do not have any difficulties that cannot be dealt with. It was just simpler to code and display data to the user without having to constantly remember to put in the Nz() function, or add 'Or Is Null' to SQL statements. And again, a Null indicates that a value is unknown, which...

No, actually - you're a PIA, and I wish you would go away. No doubt, but I, on the other hand, am sure - you are. You have dreamed up all sorts of thing I haven't said. That probably because you apparently don't understand anything I've written, given how you respond to it. And exactly THAT...

"An explanation that the typical poster here can understand." Now you're adding condescension to your endearing traits? I have a better opinion of people on this forum than you apparently do - I'm sure people here could understand an accurate explanation of nulls, like my comparison to a...

I do understand how to use them. You didn't seem to, since you wrote incorrect statements like claiming a null is a different version of nothing, which is why I took the trouble to explain some of my use case. But I agree that what you have contributed to this conversation is pointless.