Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The same LOAD statement with one field commented in and out: The first (1) one does not work and shows a script error (without saying what is wrong).The second (2) is processed without error. Yes, the field is existing in the QVD, see item (3)! Just to be sure that it is not the trivial case.
Questions: How can this be? Is the QVD (partially) corrupt? How to fix it?
Thanks for any idea or help!
(1)
LOAD XOPPLDAT,
XOPPWLT,
XOPPWAK,
XOPPWPR,
XOPPWZL
FROM
(qvd);
(2)
LOAD XOPPLDAT,
XOPPWLT,
XOPPWAK,
// XOPPWPR,
XOPPWZL
FROM
(qvd);
(3)
<QvdFieldHeader>
<FieldName>XOPPWPR</FieldName>
<BitOffset>0</BitOffset>
<BitWidth>15</BitWidth>
<Bias>0</Bias>
<NumberFormat>
<Type>UNKNOWN</Type>
<nDec>0</nDec>
<UseThou>0</UseThou>
<Fmt></Fmt>
<Dec></Dec>
<Thou></Thou>
</NumberFormat>
<NoOfSymbols>20806</NoOfSymbols>
<Offset>709841</Offset>
<Length>500918</Length>
<Comment></Comment>
<Tags>
<String>$numeric</String>
</Tags>
</QvdFieldHeader>
Although there is no evidence at all for it I assume that the encryption software for the strong authentication may cause such issue. We face other problems with the encryption software, too, as it locks randomly some files of the environment.
Hope someone profits from this experience 🙂