import not exacting?

[Kenneth Brody]

On 5/6/2014 1:26 PM, Fairlight wrote:
> I'm using import in some code, and noticed that I was ending up with
> 4-digit zipcodes after the import.  Thing is, they're ones which start as a
> zero.
>
> If I were using a cast variable for intake, I'd expect this.  However, I'm
> using a wholly uncast variable.  Shouldn't it import -literally- into an
> uncast variable?

Can you show the actual processing?  A simple import ascii will not strip 
any leading zeros, unless you put the result into a numeric field.

> I'm getting very lucky that lookups seem to match on key field, even with
> this screwy non-literal lead-zero translation.  It's always worked, so it's
> gone unnoticed until now.  But technically it should always be five digits,
> even uncast.

Can you double-check that the field is not a numeric field?  That would 
explain both scenarios.

-- 
Kenneth Brody