UnicodeSCANStmt < Main

---+ SCAN Statement

%TOC%
---++ Overview

The SCAN statement should allow Unicode and National field types to be used as both a source and a destination.
---++ Test Plan

   1 SCAN a National field from a file into a Raw work field (with/without transcode error) and a Unicode field
   1 SCAN a Unicode field from a file into a Raw work field (with/without transcode error) and a National field (with/without transcode error)
   1 SCAN a Raw field from a file into a National field (with/without transcode error) and a Unicode field
   1 
---++ Bugs

   1 %RED%%BLACK%SCAN display does not correctly display National characters. <strong>* FIXED *</strong> 7/27/11 via changes to NSCAN processes. Changed SCANDISP REC to a Label GA.%ENDCOLOR%%ENDCOLOR%
   1 %RED%%BLACK%SCAN display does not show any records from a Unicode keyed file <strong>* Tested Ok - 3/1/13 *</strong>%ENDCOLOR%%ENDCOLOR%
   1 %RED%%BLACK%When entering a starting key, display starts one record after the expected value. Run the (VIEW) BEGNAT process, go into key entry, then SCAN. For a starting value, enter Ã&dagger;. Records will be displayed starting with Ã&Dagger;, which is the next value.<strong>* Tested Ok - 3/1/13 *</strong>%ENDCOLOR%%ENDCOLOR%
   1 %RED%%BLACK%The display does not line up properly. Run any report & scan on the Form field. The data from the Form file does not line up with the headings. <strong>* Tested Ok - 3/1/13 *</strong>%ENDCOLOR%%ENDCOLOR%
   1 %RED%%BLACK%The starting fields displays the Unicode Replacement Glyph for blanks. Same example as above, scan for a form name, and enter PDF as a starting value, it will display as "PDFï¿½?ï¿½ï¿½X" - *** FIXED ** in Dec 10 engine* %ENDCOLOR%%ENDCOLOR%
   1 %RED%%BLACK%Unable to scan on field names in ILF editor, (VIEW NSCAN SETUP (FULL) crashes. <strong>* Tested Ok - 3/1/13 *</strong>%ENDCOLOR%%ENDCOLOR%
-- Main.PeteBrower - 2011-03-21
This topic: Main > WebHome > UnicodeTestPlan > UnicodeSCANStmt
Topic revision: r6 - 2013-03-01 - JeanNeron