Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
bwisealiahmad
Partner - Specialist
Partner - Specialist

Some questions

Got some questions:

  • Is there any way to script in the script editor so this shows where to put a breaking point in the debugger? Or a more favorable way of of commenting so that this helps out when debugging and where to put breaking points?
  • Can you nest Date# functions? Like Date(Date#(Date# 'DD-MM-YYYY'), D/MM/YYYY)) if you have different formats? Or do you use ALT for this?

Two questions that can't seem to to find an answer for.

Thanks for all help!

1 Solution

Accepted Solutions
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

I've never found breakpoints to be useful because there isn't much you can see in the debugger.

// and /* comments don't show up in the Document log. REM comments do. So if you want your comments to show up in the log to aid debugging, use REM.

Another debugging trick is to use the TRACE statement to write data to the log.

I also use a couple of Qlikview Component routines in my debugging.

Qvc.InspectTable  -- pauses the script and lets you browse a table.

Qvc.TableStats -- logs row and field counts. Useful for seeing row counts before and after JOIN.

When testing for different potential date formats, I use Alt()..

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

View solution in original post

6 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

I've never found breakpoints to be useful because there isn't much you can see in the debugger.

// and /* comments don't show up in the Document log. REM comments do. So if you want your comments to show up in the log to aid debugging, use REM.

Another debugging trick is to use the TRACE statement to write data to the log.

I also use a couple of Qlikview Component routines in my debugging.

Qvc.InspectTable  -- pauses the script and lets you browse a table.

Qvc.TableStats -- logs row and field counts. Useful for seeing row counts before and after JOIN.

When testing for different potential date formats, I use Alt()..

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

bwisealiahmad
Partner - Specialist
Partner - Specialist
Author

Thanks for responding regarding the scripting / breakpoint.

Reason I am asking is I remember these from the latest qv certification and got quite confused. Regarding the

Date(Date#(Date# related question I am wonder if it is possible or not? Or to do Date#(Date(Date(

Never seen it in practice, but really confused me.

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

I don't know about the nested Date#(). Give it a try and let us know what you find out. As I said, I've always used Alt() which works for my needs. Guessing at dates is always a challenge.

1/12/2015

Is that MM/DD/YYYY or DD/MM/YYYY?

-Rob

Not applicable

Hi Ali,

Where you able to get the correct answer of the first question?

Also, Can you let me know more about the exam, I am thinking of taking it soon

d44973694
Contributor II
Contributor II

I don't think that the REM statement appears in the log file. Only Trace does. REM can just have working breakpoint on it.

I included these 2 statements in my script

SCRIPT.JPG

and here is the snapshot from  log where only Trace statement can be seen, not the REM.

TEST.JPG

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

I think that's a bug. The text appears in QV11.20, but not in QV12.10.  Also, apparently from your screenshot it is asterisks in QS as well.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com