topic How to save trace - output to file (???) in QlikView

How to save trace - output to file (???)

Fri, 11 Sep 2009 19:15:40 GMT

Hi community-members,

there is the nice option in QlikView for every document to "generate logfile"(s) for every script load.

So far so good.

Now I had the problem that a document never stopped (because of 140 fields in two tables with the same name, so QlikView tried to match/link all fields [:O]).

So I wanted to put some information to the trace and copy the trace, but when QlikView never stops the script-load you are not able to copy the trace output in the debugger window (you are not able to copy the output because the debugger refreshes the output several times a second).

So my question:
Is there a (hidden or for me unknown) possibility to save the trace of the debugger to a file?

Thanks in advance

& best regards

Stefan

How to save trace - output to file (???)

hector — Fri, 11 Sep 2009 21:05:45 GMT

Hi, have you tried the option "Generate Log File"? in the "Document Properties/General", it creates a .log file in the same directory of your model.

Good Luck

How to save trace - output to file (???)

Fri, 11 Sep 2009 21:09:31 GMT

Yes, that's the problem (as described above) ...

The information in the logfile is not equal to the trace-output ...

I'd only like to have the trace-output!

Best regards

Stefan

How to save trace - output to file (???)

hector — Fri, 11 Sep 2009 21:25:09 GMT

Sorry, i've read it just the beggining so fast and it's too early here hahaha ,

I don't know an option to do that, but i find a bug xD

This is my script

Load
rowno() as ID
autogenerate(100);

but when i debug, this "window" show me this

--- Script Finished ---

then, when i press Close, the log is write after this line, "AUTOGENERATE 100 lines fetched"

anybody has the same issue?

regards

How to save trace - output to file (???)

Sat, 12 Sep 2009 17:32:48 GMT

[quote user="Héctor Muñoz"]

Sorry, i've read it just the beggining so fast and it's too early here hahaha ,

I don't know an option to do that, but i find a bug xD

This is my script

Load
rowno() as ID
autogenerate(100);

but when i debug, this "window" show me this

--- Script Finished ---

then, when i press Close, the log is write after this line, "AUTOGENERATE 100 lines fetched"

anybody has the same issue?

regards

Sorry, I do not understand your problem ...

best regards

Stefan

How to save trace - output to file (???)

hector — Mon, 14 Sep 2009 21:02:45 GMT

Hi, I'm talking about this.

It's so fast, so i made a little video.

Regards.

How to save trace - output to file (???)

Mon, 14 Sep 2009 21:13:10 GMT

hijacking threads = not cool

How to save trace - output to file (???)

Mon, 14 Sep 2009 23:08:11 GMT


dragonauta wrote:
hijacking threads = not cool<div></div>

What do you mean?

How to save trace - output to file (???)

Mon, 14 Sep 2009 23:09:01 GMT

[quote user="Héctor Muñoz"]

Hi, I'm talking about this.

It's so fast, so i made a little video.

Regards.

Sorry, cannot find any answer in this video?

Best regards
Stefan

AW:Re: How to save trace - output to file (???)

biester — Mon, 14 Sep 2009 23:42:01 GMT

Hi Stefan,

Obviously dragonauta means that Hector hijacked your thread (not posting one of his own, but "disguising" a new problem in a "reply") ...

Rgds,
Joachim

How to save trace - output to file (???)

hector — Tue, 15 Sep 2009 00:00:54 GMT

Hi, it was not my intention to "hijack" this thread, just to cooperate with more information about this issue (save trace).

And in a test that I did, this "bug" shows, obviously if the "trace window" has bugs or errors, this request can't be done.

I've tried to show this bug, the text "100 lines fetched" is AFTER the line "script finished"

Sorry if i've changed the way of this thread, i will not post anything about my issues in the future.

C ya

How to save trace - output to file (???)

Oleg_Troyansky — Tue, 15 Sep 2009 00:40:38 GMT

The only thing remotely relatedto your problem is the following setting. It might help you get the logfile even if QlikView can't finish executon. The following is a copy from the Help article about User Preferences:

Flush script log after each write

For performance reasons, the script log is normally not written to disk after each individual statement. By selecting this script box it will be. This may be useful if you use other programs to monitor the script execution via the log. However, using this setting may significantly increase script execution time in cases where the script contains large numbers of statements.

How to save trace - output to file (???)

Thu, 01 Apr 2010 10:58:01 GMT

hi,

I agree that the last statement is written after the sentence "Script finished." i think it's not so much correct!!!
very, is there a way to test in a load, the contents of the fields for each recordset loaded?

otherwise what purpose has put red dots in the script?

Mauro

How to save trace - output to file (???)

cesaraccardi — Thu, 19 May 2011 19:50:42 GMT

Hi,are you talking about the debugging option? There you can see step by step how your script is running and the data is getting loaded.

Regards,
Cesar

Re: How to save trace - output to file (???)

frank_bossuyt — Fri, 14 Mar 2014 12:57:05 GMT

Might be a bit late but this should do the trick

instead of using the 'trace' function use the 'execute' function to use a command line command to send text to a log file. Don't forget to set the option 'Can Execute External Programs'.

//initialize the file

Execute cmd.exe /c echo filename.qvw > c:\temp\log.txt;

//append to the file

Execute cmd.exe /c echo line 1 >> c:\temp\log.txt;

.........

Execute cmd.exe /c echo line 2 >> c:\temp\log.txt;

........