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

[#1]

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

[hector]

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

[Oleg_Troyansky]

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.

[#4]

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

[cesaraccardi]

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

[frank_bossuyt]

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;

........

........