import not exacting?

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Fairlight
> Sent: Tuesday, May 06, 2014 4:15 PM
> To: filePro Mailing List
> Subject: Re: import not exacting?
> 
> On Tue, May 06, 2014 at 02:14:37PM -0400, Kenneth Brody thus spoke:
> >
> > 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.
> 
> Unfortunately, no.  NDA.
> 
> > >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.
> 
> It's definitely not cast to anything.  "declare LAZip"  That's it.  What was -more-
> interesting was when I tried to put in a single looping line of logic to prepend
> zeroes on with concatenation if the length was < 5, it refused to trigger.
> Bizarre.

Mark,

If you are importing zip codes from an Excel created csv file, more than likely the leading zeroes have been stripped off.   I ran into this problem a few years back and had to import the zip code into a rj0 field to replace the leading zeroes  that had been removed.

Not sure if this is your problem, but that's how I solved my problem.


Richard Kreiss
GCC Consulting

Office: 410-653-2813