Hello Rhys Bradbury,
Thanks for your interest.
One of the reasons you are experiencing this problem - is that QlikView Expressor can currently read only .QVX files that are created by the Write QlikView operator only.
Let me review your discussion thread in depth and will further respond if I have more information to share.
Rhys - one more thing.
I am curious as to why you would perform this step:
"So i opened these .txt files saved them as QVD then stored them as QVX ready to use in a new dataflow."
...and not just use the Read File operators to source your data instead in the dataflow and therefore write to QlikView using the Write QlikView operator.
our target implementation would to be to perform incremental reloads in qlikview, generating QVDs.
Then Expressor would pick up those qvds, perform business logic operations based on rules and output to QVXs and Database.
Those QVXs will be used by ceveral QlikView Dashboards.
in reply to the reasoning behind importing the .txt to qv, then storing as a qvx would to recreate the same process which i had been doing originally -
DB>QV (export QVX)>Expressor(QVX)>(eventually QV dashboards)
(.txt)>(qvx) >(output qvx) > to be sourced to qv dashboards
(i was basically recreating the same steps as our current arcitecture)