>I see your point. Further, I think we're in agreement here on what's happening. However, my point wasn't whether or not this works, but whether or not the documentation coincides with that behavior. Clearly, it states that memory variables should be surrounded with quotation marks. Further, it goes on to say that if you don't "U" is returned. That fact that in your example above not doing so returns "N" contradicts the docs.
>
>Personally, I think that this should be passed on to the documentation team. I would hope that you'd be in agreement.

I agree with that the docs are misstating the result of passing a memvar without quotes. The result of passing a memvar wihtout quotes is not always U. I this the data type of the thing in the memvar. I think the docs are rying to explain that if want to know teh data type of a memvar you must put it in quotes, if you don't you get the data type of the contents of the memvar, which can also be a confusing statement. But this shows what I mean;

lcVar = "123"
type(lcVar)

the contents are numeric

lcVar = "ABC"
type(lcVar)

the contents, that is a variable for field named abc is U

lcVar1 = "123"
lcVar2 = "lcVar1"
type(lcVar2)

the result is C because lcVar2 contains lcVar1 and lcVar1 is character type.