Where have I to set the QvWorkPath or the QvPath

[#1]

When i debug my Script I see each time a other QvWorkPath or the QvPath as I need.

Where have I to set the QvWorkPath or the QvPath?

"

WinRoot    "C:"

vLastExecTime    10.11.2011 11:01:25

QvWorkRoot    "C:"

1    1

vFilterDate    "to_date(substr('20090101', 1, 8),'yyyymmdd')"

OpenUrlTimeout    86400

WinPath    "C:\Windows"

0    0

QvWorkPath    "C:\D\QVSHARE\SOURCEDOCS\STSBI_ABAS"

QvRoot    "C:"

QvPath    "C:\D\qvserver\Distribution Service"

CD    "E:"

FLOPPY    "A:"

"

[Anonymous]

They are system variables auto defined by QlikView.  The QV Desktop Help describes them.  Below pasted in from the Help:

QvWorkPath

Returns the browse string to the current QlikView document. A system-defined variable.

QvWorkRoot

Returns the root directory of the current QlikView document. A system-defined variable.

[pokassov]

Hi Matthias!

1 step

2 step

[#4]

@Cepreu pokacow,  Thanks. It was very helpful for me.

[#5]

@Bill Markham, in Generator you could not change it. But I work in the moment with the App's

[Peter_Cammaert]

Where? You don't.

Why would you want to change the value of a variable like QvPath? So that QlikView Desktop/QlikView Distribution Service cannot find it's own executable anymore? Not good...

The strange values you get in the variable overview may be a remnant of a previous execution in a different environment.The values of these variables are (re)set at the beginning of every script execution.

[#7]

Because I have Generator and a App which are ok. But I need Generators for other parts aof the database. Thats why I copied the Generator and the App, because to test the program the other generator und app, with the old.

[Peter_Cammaert]

That's just fine with me. But does it mean that another QlikView engine should reload the data as well (QvPath)? Or that the path of the copy of Generator and App should be changed into something entirely different?

The System will set these variables to the correct values.

For your test/debug copies, the folowing will happen immediately before the first debug/test script line is executed,

• QvPath will be set to the location of the reload engine of choice, which is QV Desktop or the QVB subprocess of QDS if you start/trigger a reload task in the QMC .
• QvWorkPath will be set to the location of the debug version of Generator (for the Generator QVW) or the debug version of the App (for the App QVW)

For your original documents, this is what will happen immediately before the first production script line is executed:

• QvPath will still be set to the location of the reload engine of choice, which is QV Desktop or the QVB subprocess of QDS if you start/trigger a reload task in the QMC.You don't have two QV Desktop and two QVS installations on the same machine, do you?
• QvWorkPath will be set to the location of the (old) production version of Generator (for the Generator QVW) or the production version of the App (for the App QVW)

I hope this sheds some light on the situation. If not, ask away.

Peter

[Peter_Cammaert]

Note that - if I'm not mistaken - the value of QvWorkPath may change during the execution of the script and whenever the script encounters a Directory; statement.

[#10]

The path of the copy from the Generator and App should be a other path as before.

I have a under /config a datafile "project_paths" for this, but that he had ignore by the debugging. That's why i want to make this fix and it's ok so.

"

LET vDir_base = 'K:\Elger\StBi_neu\qvshare';

LET vDir_scripts = vDir_base & '\_scripts';

LET vDir_qvd      = vDir_base & '\daten\qvd\' & vERP & vAppName;

LET vDir_xls     = vDir_base & '\daten\xls' & vAppName;

LET vDir_csv     = vDir_base & '\daten\csv' & vAppName;

LET vDir_parameter = vDir_base & '\daten\xls\_parameter';

LET vDir_images  = vDir_base & '\daten\img';

// temp. until globals param include

SET vParameterFormat='xlsx'; // xls / xlsx (later may be qvd)"

"