Not sure but Ref manual has something on this as direct query uses source database to fetch measure fields,
as it says -
Differences between Data In-Memory and Database Data
QlikView is case-sensitive when making associations with in-memory data. Direct Discovery selects data
from source databases according to the case-sensitivity of the database. If a database is not case-sensitive, a
Direct Discovery query might return data that an in-memory query would not. For example, if the following
data exists in a database that is not case-sensitive, a Direct Discovery query of the value "Red" would return
all four rows.
an in-memory query may produce more matching values than a Direct Discovery query.
The matches returned for Direct Discovery data depends on the database.
Case sensitivity is completely irrelevant in this situation.
You also missed the point of my question. So to clarify:
Given two separate QVW files, where the only difference is the querying method (in-memory vs direct discovery):
When the selections on each ARE THE SAME (i.e. I'm making a selection on machineDesc and colDesc in EACH qvw), the values reflected in the table box are the same (one row in each table box), I can clearly see that itemDesc has a value in both QVWs. The problem is that the TEXT OBJECTs associated with that particular field (text: =itemDesc) are displaying different values. On the in-memory QVW, I get the same value as reflected in the table box. To my knowledge, this works as designed and is what I expect. On the direct-query QVW, I get a NULL value in the text object, even though the table-box CLEARLY SHOWS a value.
My question is why? I'm getting one value from the in-memory. I'm getting the exact same value from the direct-discovery. Why are the text objects different?