Specific fields causing 1% of rows to not load in a SQL Select QVD load

[#1]

In the Sql select load statement below, if I uncomment "PART_NO,
800+ fewer rows out of 180,000 are found. Does anyone else have this sort of problem where
certain fields are causing a few rows to not load?
Does anyone have any suggestions for troubleshooting or correcting incomplete SQL loads?

OrderLines:

LOAD

//"PART_NO" AS OrderLines_ItemNbr,

"MCODE" AS OrderLines_MfgCode,

"ORDER_NO" AS OrderLines_OrderNbr,

"LINE" AS OrderLines_OrderLineNbr

SQL SELECT

//"PART_NO",

"MCODE",

"ORDER_NO",

"LINE"

FROM "ORDER_LINE";

STORE OrderLines INTO [UV_OrderLines.qvd];

[#2]

I don't know, but I will check.

[#3]

It's a table, but the table is from a multivalue database from IBM called Universe.
The ODBC connector splits some of the actual tables into virtual tables to normalize
so SQL scripts can be used.

[rbecher]

So, then I would double check this behavior with a different tool via ODBC.

Is this an online database with write operations? Maybe it's an issue with read/write consistency (transaction level).

[#5]

Good point. I will do this and let you know the results.