Every time you want to convert the currently loaded document into a demo version of itself inside the QV Desktop, you're limited to what the desktop will allowe you to do. Which is not very much if you look at it from a multripl-document-management viewpoint.
IMHO I think it's better to start writing a VB/C#/VC++ application and use the QlikView OCX component to load-modify-save whatever document you need to transform and according to the rules for creating a demo version that you define yourself.
There are a few advantages:
- You can do almost anything with your QVW(s), including dropping the script, hiding or removing sheets, deleting objects, reloading with specific settings to get a limited data set for dmeo purposes etc.
- You can process them in batch
- You can construct a rule set that is applied by default to all docs or just to some very specific documents
- You can set variables to specific values that act as a sort of programmable expiration date (sheets go blank after a specific date)
- You can fully automate the process
- etc.
There is one big disadvantage:
- Since I don't know if someone has ever tried writing such a tool before, and since I don't know the amount of work you're facing when creating demo versions, I will probably be too complex/expensive for you to try and create it all by yourself.
Hmm,
Peter
