weird import behavior

[Jean-Pierre A. Radley]

Mitch Theophila/MGT Computer Solutions propounded (on Thu, Jan 20, 2005 at 01:10:44PM -0500):
| out of 13000+ records imported, a dozen or so had 0xF8 or 0xB0 
| characters in import field 3.  fields 1 and 2 had no such 
| instances. 
| 
| here comes the weirdness.  
| 
| after the import, in only the new records created from these 
| dozen or so, only the numeric value from import field 2 (now 
| in file field 4) had been imported.  when viewing these records 
| in *clerk via a defined screen, fields 1 and 20 (from import 
| fields 1 and 3) appeared to be blank. 

What's weird about that?
Any input with 0xf8 or 0xb0 is going to fail the ALLUP edit, which
accepts characters from chr(0x20) to chr(0x7e), 

-- 
JP