Sometimes I have to export data with fields that are all digits but are really character fields like PatientID, ClaimNumber, or similar where leadings zeros are necessary. I often prefix the field with an underscore to avoid have Excel screw me over.
hth, --Mike
On 2016-02-28 19:19, Sytze de Boer wrote:
The Supplier code could be letters and number, just letters, or just numbers.
The supplier code may be 12345.1234567890 It's nothing to do with decimal point. It's a character. If the code is ABC12345.1234567890 all is fine.
The import routine is append from file IMPFILE type csv
On Mon, Feb 29, 2016 at 1:15 PM, Joe Yoder joe@wheypower.com wrote:
I only dabble with Excel but I suspect that you can get your expected results by setting it up to use five decimal places instead of two. I thought you could convert it in Foxpro with str(val( '12345.56'), 10, 5) but for some reason that only gives 4 decimal places even with decimals set to 6. I guess that leaves string manipulation where you find the location of the dot from the right edge of the trimed string with the RAT function and add as many zero as you need.
I'm curious why the extra zeros are important.
Joe
On Sun, Feb 28, 2016 at 6:36 PM, Sytze de Boer sytze.kiss@gmail.com wrote:
I have a problem and I hope someone can help
I export 3 fields to a CSV file Code C(15), price N(10,2) , supcode C(30)
The code and the supcode may be pure numbers Example supcode may be 12345.56000
I make some changes to the price (using Excel) I now import from this same file and the supcode has changed to 12345.56
Whats the best way to overcome this?
-- Kind regards, Sytze de Boer
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]