New version Calcpad VM 7.2.1 was released.

[Proektsoftbg]

Dear friends,

Calcpad VM 7.2.1 was released with new commands for import/export of text, CSV and Excel files:

Text/CSV files:

#read M from filename.txt@R1C1:R2C2 TYPE=R SEP=','
#write M to filename.txt@R1C1:R2C2 TYPE=N SEP=','
#append M to filename.txt@R1C1:R2C2 TYPE=N SEP=','

Excel files

#read M from filename.xlsx@Sheet1!A1:B2 TYPE=R
#write M to filename.xlsx@Sheet1!A1:B2 TYPE=N
#append M to filename.xlsx@Sheet1!A1:B2 TYPE=N

This version is currently available for project sponsors and contributors only. Please support the Calcpad development on GitHub and get regular updates and early access to the latest features:

https://github.com/sponsors/Proektsoftbg

[Erikbernhart]

Hi Ned, i tried the 7.2.1 version, and i love the possibilities that this brings us.
is it correct that that imported data is converted into integers?
15.99 becomes 1599 and so on. or did i miss something

[Proektsoftbg]

Hi!

No, it is not converted to integers. Probably there is some parsing or data format problem.
On my side it works.

Can you please share this table? What are your regional settings? What is the decimal separator there? this can also cause problems. If it is comma, parsing to double can treat it like digit (thosands) separator: 1,234,567.89

[Erikbernhart]

yes i think the regional settings messed with this one, here in NL the standard for decimal is a comma, among excel files this causes no problems, but here it did mess it up. when i changed it to . as decimal separator it worked. thanks

[henriqueralves1]

hi. am i doing something wrong here with the separator? is there a solution withou having to change the regional settings?

[Proektsoftbg]

Hi! It is not that simple.

The problem is related to Calcpad, but there is a difference in the ways how Excel displays the numbers and how it stores them internally in the xlsx file. In the file it is always a dot. At least on my version Office 365 - latest. Check the string value in debug. Is it with comma or dot?

But if you save the file as CSV, it will be always comma. So, I made it to try both in the last revision and it worked. With your fix, it will try only comma and will throw the exception if fails without going to the second line. So we are going back to where we were 4 days ago when @henriqueralves1 reported.

It will actually work if you replace both lines 413 and 414. Try this code:

            if (n > 0 && 
                !double.TryParse(numberSpan, CultureInfo.InvariantCulture.NumberFormat, out d) && 
                !double.TryParse(numberSpan, numFormat, out d))
                throw Exceptions.InvalidNumber(numberSpan.ToString());

[javila]

[javila]

It will actually work if you replace both lines 413 and 414. Try this code:

            if (n > 0 && 
                !double.TryParse(numberSpan, CultureInfo.InvariantCulture.NumberFormat, out d) && 
                !double.TryParse(numberSpan, numFormat, out d))
                throw Exceptions.InvalidNumber(numberSpan.ToString());

I expect it will work, since the last parse command will overwrite the first. But then the issue you said will still be there, no?

[javila]

Well... If we are talking about regional settings with comma as decimal separator, the error should be expected when you try to parse 11.11 (since it's not a number in regional settings)?

[Proektsoftbg]

@javila Maybe you tried to post an image, but it is not accessible for some reason. Anyway, I think we have found some solution for now but in future will dive deeper into the problem and find a way to make it work for any possible settings. I highly appreciate and thank you for being so active and helpful on this topic and many others as well, spending a lot of your time. But such discussions really helps to know what are the traditions in different countries and make the software better and more suitable for use.

[javila]

Hi, @Proektsoftbg.

I was just trying to help. Really. IMHO, Calcpad shouldn't bother with CSV files using comma as decimal separator. The user could simple replace the commas with dots using any text editor. Anyway, as you said, it can work with a DEC=',' reading option that can be used inside the ReadCSV() function to quickly replace the character with a dot if you want to. There are some options to solve this problem. Even saying people should use dots in a CSV is a valid one. What we can't do is asking people to change their regional settings in order to make the software work. 👍