IMPORTANT ANNOUNCEMENT

These forums were permanently set to read-only mode on July 20, 2022. From that day onwards, no new posting or comment is allowed on the site, but the historical content remains intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Page 2 of 2 < 1 2
Topic Options
#49584 - 10/06/14 11:12 AM Re: Using Comma Delimited CSV [Re: Philippe F.]
strido Offline
OL Expert

Registered: 08/06/13
Posts: 159
Loc: MA
I think I'll edit this again blush

I've gone ahead and used the ODBC with a comma delimited text file. The CSV was created in Excel and saved as a .CSV.

Using the database emulation removes the leading zero from the zip code though. Have we seen this and / or have a solution for it? When saving the .CSV file from Excel I specified that column to be a zip code, and determined on my desktop that it indeed stays. Only when using this database emulation does it remove the zero. Changing the emulation back to a CSV returns the zero.


Edited by strido (10/06/14 02:08 PM)

Top
#49651 - 10/08/14 05:57 PM Re: Using Comma Delimited CSV [Re: strido]
jim3108 Offline
OL Expert

Registered: 04/19/10
Posts: 316
Loc: London, UK
That is why I always use an ASCII emulation and the CSV Indexer function as the emulation then treats the CSV file as a text file reading all lines and characters regardless.

Top
#49668 - 10/09/14 01:30 PM Re: Using Comma Delimited CSV [Re: strido]
Benoit Potvin
Unregistered


When using the DB emulation, you can put back those zeroes with PlanetPress Talk like this:

Code:
= right('00000' +Field('ZipCode',1),5)


this expression keeps the 5 rightmost characters of a string that is '00000' concatenated to the value of the zipcode db field.

hope this helps

Top
Page 2 of 2 < 1 2