|
I can't speak for anyone else, but my customers did not like this as a solution. Mike E. "Johnson, Duane" <djohnson@xxxxxxxxx To: "'RPG programming on the AS400 / iSeries'" .com> <rpg400-l@xxxxxxxxxxxx> Sent by: cc: rpg400-l-bounces@xx Subject: RE: AS400 to EXCEL drange.com 05/20/2003 01:48 PM Please respond to RPG programming on the AS400 / iSeries I haven't been paying a great deal of attention to this thread, so I might have missed a similar suggestion, or you may have already given a reason why this wouldn't work. If so, please forgive me. Is there any reason why you can't run your information to a separate file, placing all your numeric fields into a character field, concatenating a character to the beginning - i.e. 007644 would become, for instance, C007644. This would prevent Excel from removing the leading zero's. Then you could build a macro for this particular file that, once loaded into Excel, would remove the first character from each of the numeric fields. I suppose it is possible that at that point, Excel would then take it upon itself to remove those disgusting leading zeros, but if not, that should work. Duane > -----Original Message----- > From: Douglas Handy [SMTP:dhandy1@xxxxxxxxxxxxx] > Sent: Tuesday, May 20, 2003 9:49 AM > To: RPG programming on the AS400 / iSeries > Subject: Re: AS400 to EXCEL > > Booth, > > >Is this also true if the CSV fields are all enclosed in quotes? Not > >apostrophes but quotation marks. > > In Excel, it still considers it a numeric value and drops the leading > zeros > despite the presence of the quotation marks. Silly, but true. > > >"John Smith","001234" > > Not in Excel it doesn't. The second cell will be right-adjusted and the > value > displayed will be simply 1234. Even applying a cell format of "text" at > that > point will leave it as 1234 (albeit now left-justified). So the leading > zeros > are lost during the file open / import process. > > Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.