Analysis

  • Status Assigned
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Parser
  • Assigned To
    Torsten Bonde Christiansen
  • Operating System All
  • Severity High
  • Priority High
  • Reported Version 1.3.2
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Analysis
Opened by Jens Lauritsen - 28.01.2019
Last edited by Jens Lauritsen - 28.01.2019

FS#190 - Value label: Incorrect handling of in-existing values in modification

Two aspects of modifications of value labels are not handled in a user oriented manner.

1 change to "not found": // value label should be forgiving if deleting a value is not found, just like "drop v " .

for S in ["alvorliglbl", "fvgl","janej","henvislbl","koenlbl","plbl"] do

edit vl @{s} !d:=1410065407;

ERROR: Cannot delete - value does not exist!

2 change to "Cannot Assign Missing to undefined Value in: xxxx (here alderlbl)"

// Assigning missing to an undefined value is not handled correctly

edit vl alderlbl !m:=9;

ERROR: Unhandled error during execution:

Access violation

Please contact EpiData (info@epidata.dk) and include a copy of history and if possible example data!

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing