SYSTEMVAR$ reads or sets Quaestor system SYSTEMVAR$ reads or sets Quaestor system variables

Syntax

1. SYSTEMVAR$(VarName$)
2. SYSTEMVAR$(VarName$, Setting$)
    

 Arguments

• VarName$ is the name of the Quaestor system the Quaestor system variable. The string value should be between quotes and is not case sensetive. Every Quaestor system Every Quaestor system variable can be read. Of some variables also a value can be set (see remarks below for all variables).
• Setting$ is the additional set value for VarName$. The type of value (string or integer) will depend on the type of VarName$

Remarks

1. SYSTEMVAR$ is mainly used in combination with knowledge bases to be used on the server functionality of Quaestorof Quaestor. However, some of the read only variables are also useful for any knowledge base;
2. The following Quaestor system following Quaestor system variable can be set and read:
   1. "qi_ranges", set the maximum number of parameter variations (give a value), default is unlimitted;
   2. "qi_acceptall", set

...

1. 1. the Workbase to accept all proposed values and relations (same as the right mouse menu option in

...

1. 1. the Workbase), default value is "N":
      • • "qi_acceptall"="y" do accept all
        • "qi_acceptall" = "n" do not accept all
      • "qi_succes", can be set in order to communicate to the outside World (when working as server) that no succes is achieved. The value is by default "0" at the start of

...

1. 1. • a Solution and "1" when the top goal is achieved. You can set this value to your own judgement using

...

1. 1. • the SYSTEMVAR$ function:
        • "qi_succes"="0" no succes
        • "qi_succes" = "1" succes
2. The following Quaestor system variable can be following Quaestor system variables can be read only:
   
   1. "qi_username", returns the user name. Either provided from Windows or from another source such as eGroupWare;
   2. "qi_headless", return whether Quaestor is whether Quaestor is running as client or as server:
      1. "qi_headless" = "y", Quaestor is  Quaestor is running as server;
      2. "qi_headless" = "n", Quaestor is  Quaestor is running as client;
   3. "objectname", provides "NullString" when not in an object or the name of the object it is part of;
   4. "qi_delimiter", give the type of delimiter used to provide ranges (either , or ;)
   5. "reportpath", returns the string of the total report path in Windows format (as set under Tools>Options);
   6. "htmlfilereportpathhtmlfilereportpath", returns the string of the total report path in proper HTML browser format;
   7. "unixreportpathunixreportpath", returns the string of the total report path in unix format (with forward slashes);
   8. "kbspath", returns the string of the knowledge base path in Windows format (as set under Tools>Options);
   9. "apppath", returns the string of the general application path in Windows format (as set under Tools>Options);
   10. "appkbspathappkbspath", returns the string of the  knowledge base application path in Windows format

Examples

See Directory structure for the Quaestor standards the Quaestor standards concerning the directories. Assume a knowledge base with the name KnowledgeBaseName
ReportPath$ = SYSTEMVAR$("ReportPath")

will return
"E:\My Documents\My Knowledge\Projects\_KnowledgeBaseName\Solutions\"

HTMLFileReportPath$ = SYSTEMVAR$("htmlfileReportPath") 

will return
"file://E:/My Documents/My Knowledge/Projects/_KnowledgeBaseName/Solutions/" 

So tell the outside World that a solution is not judged as succesful:
CALC_success$ = SYSTEMVAR$("QI_success","0")

Example knowledgebases

Download 

An example knowledgebase of this function can be donwloaded here 

Quick links: Functions overview | Attribute overview | Constants overview | Dimensions overview