Page History

...

• Mode% controls the modus of EXCEL (0 if you don't want to see the sheet, 1 if you want the sheet to be visible).
• SourceSheet$ is the file name of the Excel sheet.
• If no path is included in the string for SourceSheet$, the file is expected to be in the applications directory of the knowledge base (see also Directory structure ).
• If "NullString" is provided as value for SourceSheet$, the sheet has to be embedded in the expression using the right mouse option "Include Binary in frame...".
• TargetSheet$ is the name under which the created Excel sheet will be saved.
• If no path is included in the string for TargetSheet$, the file is saved on the current Report/Project (..\My knowledge\Project\..) directory of this project (see also Directory structure ).
• If "NullString" is provided as value, the sheet will not be saved at all.
• TelitabInput$ is the dataset that can be used as input for the calculation (not required as long as all data required for InputScript$ is available).
• InputScript$ is the input script (in TeLiTab format) in which the positions in the spreadsheet are stated.
• OutputScript$ is the output script (in TeLiTab format) in which the positions are given of the data in the sheet to be presented as Telitab$ output of the parameter using the EXCEL#() function.
  Parameters in OutputScript$ should also be defined in InputScript$ with an empty spreadsheet position when you want to receive these values as input for Quaestor. This means that Quaestor will deal with these values provided as input in the solution, while these values where originally not provided but only given to in the spreadsheet. (see also examples).
• InpVar is an optional list of parameters or expessions. The list may contain one or more parameters required by the InputScript$ of the EXCEL#() function when these are not included in TelitabInput$. In such event, the current case values of the parameters presented in InputScript$ (and included in InpVar or computed earlier) are used as input for the EXCEL file.

...

1. You should never manually close the Excel sheet that is opened by Quaestor. Return to Quaestor and click on OK in the message box that asks you whether to close Excel. If you do close Excel manually, Quaestor is unable to retrieve data from the sheet.

...

• 5 list items to be sent to Excel;
• The single-case parameter "No_cases" is put in the cell with the name: No_cases of worksheet: main_dim.
• The parameters "Lpp", "B", "T" and "Cb" have multiple entries. The writing of these values to Excel is as follows:

1. Quaestor will go to the column number corresponding with the number behind the parameter name, in the case of Lpp this is the first column;
2. Quaestor will start placing values below the point where it finds a cell with the value (not the name) corresponding to the name provided in the input script in front of the column number, in this case "Lpp";
3. The same follows for the other multi-case parameters, which are placed in their corresponding columns below the cell with value "B", "T", etc. 

...

Furthermore, you could place parameters in the same column. However, when the value represented the name of the parameter is overwritten during the process of writing the values of the other parameter in the column, Quaestor will not be able to find the overwritten value and an error will be the result.

...

• 4 list items will be sent to Excel (No_cases, TestNo, Vs and Ps);
• The parameter "No_cases" is put in the cell with the name: No_cases of worksheet: main (as in all previous examples).
• The parameter "TestNo" is the so called "Running" parameter. This parameters determines the blocks of accompanying data. When it changes its value, it will be be the indication for Quaestor change the column number (CASENO) for the block of data.
• You see that the syntax

...

1. With CASENO(TestNo) you indicate that Quaestor should calculate the case/column number based on the change of TestNo. In our example this means that Quaestor will start (by default) with 1 as result for CASENO(TestNo). The moment the value for TestNo changes from 10001 into 10002, the result for CASENO(TestNo) will be 2, so 10001 will be writen in the first column and 10002 in the second one.
2. Like a normal expression, you can carry out calculation. Thus (4+CASENO(TestNo) will start with column 5 and will change to column 6.
3. The difference in syntax between
   
   "main.TestNo(0+CASENO(TestNo)).1"
   
   and
   
   "main.Vs(0+CASENO(TestNo))"
   
   is that, by placing ".1" behind "main.TestNo(CASENO(TestNo))", you indicated that only one value should be written, while using the method to jump columns. (for the moment only .1 is supported and only in combination with the CASENO syntax)
4. Please do write CASENO in upper case.

...