Why don't you try? A QVW file is not a text file, so the editor will switch to hex-mode. At the end of the binary stream, you'll find the XML part of every QVW that can be read into QlikView through the xml-import filter.
What do you want to do with a binary file in a text editor?
We have some sql in the qvw file that needs to be updated. As there are many of these files that need to be updated, I was hoping to utilize the find/replace in files feature from either Notepad++ or UltraEdit to do this in all files in a specific folder.
My guess is that you tried with the QlikView Addict Notepad++ plugin?
That only works for the script part of the QVW file. What you can do is save as a QVS file (it's just a plain text file) File -> Export to Script File and open that file in Notepad++ or just do a Copy & Paste of the whole script.
Thanks Eduardo, but we have hundreds of files and thus I'm trying to utilize the replace in files features of either Notepad++ or UltraEdit to do a bulk find/replace. I did try the QlikView Addict plugins but as you stated that is for qvs files. Any other thoughts?
You can't open QVW file into any editor such as Notepad, Notepad++, Sublime Text, etc.
Please note, if you are looking for to replace any text/expression then here are the steps just follow them,
Open Your QlikView Application > Go to manu option called "Settings" > Expression Overview > Mark check to all of the Check Boxes > Click on Button "Find/Replace" > Write your text/expression into "Find What" Section > Write you text/expression into "Replace With" > Click on Button "Replace All" > Close > Apply > OK. Finally, Save your document with latest changes.
I don't think that this is a good idea - you will be now paying the price for hard-coding variables/paths/connections and so on instead of using external libraries for them - therefore I suggest to change this with include-variables for future changes: The $(Include) which you $(Must_Include) into your toolkit.
For your task now you could use vbs-macros to read and change the script (but be careful by replacing anything and make BACKUP's before):
I agree with Marcus. If you don't want to have to change the expressions/configuration settings/variable definitions in hundreds of QlikView documents, put them outside of the documents in either script files, include files or even an Excel file. Many of these things can be merged into a single file, making in quite easy to change a single setting that impacts all of your documents. No matter how many you'll be managing in the future.
You should especially do this for connection strings where you run the risk that a password expires and needs to be changed in all documents that access a particular data source.