LabVIEW
Convert number to string as currency!
Solved!
Hi fsteini,
like to keep the two zeros after the comma if it is an integer number.
Integer numbers don't have a "comma" (aka decimal separator char aka point in English text) by definition. And they always have "zeros after the comma".
Why don't you set the formatting of your numbers to "%.2f"?
@GerdW wrote:
like to keep the two zeros after the comma if it is an integer number.
Integer numbers don't have a "comma" (aka decimal separator char aka point in English text) by definition. And they always have "zeros after the comma".
In most of Europe, a comma is used as decimal separator (except by programmers).
Search LabVIEW like a graph! Hi wiebe,
In most of Europe, a comma is used as decimal separator (except by programmers).
I know as I live in Germany. And I force my collegues to use "English" settings when they want to handle measurement data…
But in an English-speaking forum it might be obscure to ask about "zeros after the comma".
@GerdW wrote:
Hi wiebe,
In most of Europe, a comma is used as decimal separator (except by programmers).
I know as I live in Germany. And I force my collegues to use "English" settings when they want to handle measurement data…
But in an English-speaking forum it might be obscure to ask about "zeros after the comma".
Hmm. Not sure about that. I feel it is a serious concern for English-speaking people to be aware of it. If it is obscure, it's about time to change that.
I always (successfully) try to adapt to the people's wishes. If they want comma's, everything that shows should use comma's. Of course, for everything stored, decimal points is a better choice. Reports are a grey area, and it might need a setting to specify what the user wants.
BTW: Getting off topic. %.2f sound like a solution to me.
