Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I created QVX file same like QVD, but getting error at the time of QVX load.
The QVX (Data Exchange) format introduced with V10 is intended to be used to pass data to QlikView in an optimized form directly from an external source. It is an open format with an XML based description that an external routine can write to. Hence you can use it in conjunction with a custom data connector to attach to data sources that do not have traditional ODBC/OLE-DB connectivity. Further you can use it in two formats -
1. As a persistent file format. If your target data source pushes data out you can capture it and persist to a QVX file that can be loaded as a part of your script
2. As a named pipe - if you target source exposes its own 'query' interface your custom connector and the QlikView script can support direct calls to fetch data during the load. The connector can pass the data into the script in the QVX format.
QVX is intended to solve the common request from people looking to write directly to a QVD format from an external source. Given the highly optimized nature of a QVD file, we have introduced this new QVX format to address the request. QVX is optimized though not to the extent of a QVD file.
What you don't want to confuse QVX into is the notion of storing into QVX from within a script. If you are passing data between QVW processes then a QVD is the right way. There is no advantage of using QVX in this process.
Regards
John T
Same as how you create a QVD file. What error you are getting ?
Create QVX
TestAccount:
SQL SELECT TOP 10 AccountNumber,AccountName
FROM Account ORDER BY AccountID DESC;
STORE TestAccount INTO
Load QVX
LOAD AccountNumber,AccountName FROM
error : Execution of script failed. Reload old data? Yes or No.
store * from t1 into t1.qvx (qvx);
The QVX (Data Exchange) format introduced with V10 is intended to be used to pass data to QlikView in an optimized form directly from an external source. It is an open format with an XML based description that an external routine can write to. Hence you can use it in conjunction with a custom data connector to attach to data sources that do not have traditional ODBC/OLE-DB connectivity. Further you can use it in two formats -
1. As a persistent file format. If your target data source pushes data out you can capture it and persist to a QVX file that can be loaded as a part of your script
2. As a named pipe - if you target source exposes its own 'query' interface your custom connector and the QlikView script can support direct calls to fetch data during the load. The connector can pass the data into the script in the QVX format.
QVX is intended to solve the common request from people looking to write directly to a QVD format from an external source. Given the highly optimized nature of a QVD file, we have introduced this new QVX format to address the request. QVX is optimized though not to the extent of a QVD file.
What you don't want to confuse QVX into is the notion of storing into QVX from within a script. If you are passing data between QVW processes then a QVD is the right way. There is no advantage of using QVX in this process.
Regards
John T
Hi John,
I haven't seen any example or documentation for how an external application can create a qvx file. It's not explained in the user manual. Can you point me to an example or doc?
Thanks!
-Tim
Tim,
The QVX file format is documented in a PDF that installs wit the V10 SDK.
-Rob
Issue a STORE .. INTO x.qvx (qvx) and look at the file in hex editor . It is a nice supplement to the official PDF .
-Alex
I haven't seen any example or documentation for how an external application can create a qvx file. It's not explained in the user manual. Can you provide the QV Document which explain me the same.