IF statement to replace text

Comments

• gpi

  May 2018 edited 1:56PM

  [IIF(<WO-Part."Thickness">==0.375, "3/8", IIF(<WO-Part."Thickness">==0.250, "1/2",""))]
• LurkingKiwi Wellington, New Zealand

  May 2018 edited 1:56PM

  Note that absolute comparisons to floating point numbers are generally a bad idea, as a tiny difference in the calculation can result in a minute fractional difference.
  You could compare the text version of your field to "0.375", as it will have a fixed precision, or do something like ABS(<WO-Part."Thickness"> - 0.375) < 0.001
• Polomint Australia

  May 2018 edited May 2018

  I'd like to endorse Lurking K1w1's response.
  
  And cheekily add that 0.25 is 1/4 not 1/2 (0.50)!
  
  The code above only catches two cases.
  
  Would it not be better to create a function that presents decimal amounts as the closest vulgar fraction? There are quite a few examples of code to do this, just a google away...
  
  Cheers, Paul
• Galin

  May 2018 edited 1:56PM

  Polomint wrote: »

  I'd like to endorse Lurking K1w1's response.
  
  And cheekily add that 0.25 is 1/4 not 1/2 (0.50)!
  
  The code above only catches two cases.
  
  Would it not be better to create a function that presents decimal amounts as the closest vulgar fraction? There are quite a few examples of code to do this, just a google away...
  
  Cheers, Paul

  
  
  OMG and I do this for a living!
  
  Thanks for the code! I was nowhere close. In our circumstance (still good advice for others down the road), we are very specific with our decimals, i.e. 0.375 is always written exactly that way.
• PatF

  May 2018 edited 1:56PM

  I'm with LurkingKiwi on this. The problem with float does not come in the way you "write it", but in the way it is stored or manipulated which is most of the time out of the programmer's control. Comparing fixed value might be working for you at the moment, but it will without a doubt be a problem at some point. You can't rely on comparing float value without some sort of tolerance.