Document Analyzer V1.15

[rwunderlich]

I've published an updated version 1.15 of Document Analyzer to

http://robwunderlich.com/downloads/

Changes in this update:

- Fix a hang caused by unicode values in variables or expressions. Property files are now written in unicode.

If you have any questions or problems with DocumentAnalyzer, post to this thread or email to the address given on the DocumentAnalyzer "About" sheet.

-Rob

[#2]

Hi Rob,

I can't see script running....Do you know possible causes ?

[rwunderlich]

Can you post the CollectProperties log and the document log?

-Rob

[#4]

Hi Rob,

I tried running Doc Analyzer v1.15 and it gave out of memory error. Not sure why.

Could you please help. I am attaching a screenshot and the doc analyzer log file for your reference

Thanks

raghu

[#5]

Thanks Rob for these useful tools

Have a good day

Chris

[jchoucq]

Hi Rob and thank you very much for your brillant work !

With Document Anallyzer V1.15 my "Running Script" window stays always empty and the load treatment never ends. Moreover, i don't get any log files. Do you have any ideas ?

Best regards,

Johann

[rwunderlich]

HI Johann,

Try killing the reload and then loading with a ctl-R. Let me know how that works out.

-Rob

[rwunderlich]

Hi Rahgu,

Can you zip up and post the directory

C:\Users\rdube1\AppData\Local\Temp\qvwork\Client and Investment Analytics - CopyReduced

-Rob

[#9]

Hi Rob,

I was having the same issue however reloading and using ctl-R did work.

Thanks,

Jon

[#10]

I have 2 issues I need support on. First, here are the environment details:

Qlikview v11.0.11440.0 SR2 64-bit Edition (x64)

Doc Analyzer v1.15

qvw file size: 367MB

approximate number of fields: 450

Issue 1) Cannot Process Doc

I experience an issue that when I click "Process Doc" the actual document which I have browsed is opened and then hangs (goes to a Not Responding state).

Issue 2) Fields "not in use" are actually in use

It seems that since the expressions, dimensions and variables are .csv files the analyzer does not correctly read the values if they contain line breaks. This leads to a field showing up as not in use, but it is actually in use  e.g. in a complex set analysis which contains line breaks.