Paradox Community

Items in pnews.paradox-development

Subject:Re: formatting
Date:Fri, 6 Apr 2018 14:19:57 -0400
From:"Steven Green" <greens@diamondsg.com>
Newsgroups:pnews.paradox-development
Mark, I'll try what you said.. Mike, yes, making the display "w.4" solves it

problem is, that's supposed to be "display" formatting, not "field" 
formatting.. never noticed this before.. something like this has HUGE 
implications, in theory

--

Steven Green
Myrtle Beach, South Carolina, USA

http://www.OasisTradingPost.com

Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Mark Bannister"  wrote in message 
news:5ac7b614$1@pnews.thedbcommunity.com...

That sounds vaguely familiar.....  could actually be useful if it you
knew about it and it was consistent.
Have you tried the difference of:
  usaage * tc.unitcost
vs
  usaage.value * tc.unitcost
?
--
Mark B


On 4/6/2018 11:13 AM, Steven Green wrote:
> I have a field called Useage.. no formatting or rules on the actual field, 
> just a raw Number field that often has up to 4 decimal places
>
> on a form, I display it "w.2", but I can click on the field and see the 
> actual value, if it's .025 or anything like that.. so far, normal behavior 
> that I expected
>
> but when I use that field in a calc, it's using the formatted version of 
> the field, not the real field.. in the example above, it showed me .03 on 
> the form, of course.. I clicked on it and saw .025.. it did the resultant 
> math with .03.. but I look at the table afterwards, it's .025
>
> useage * tc.unitcost
>
> in my example, tc.unitcost is 182.. times .025 is 4.55, times .03 is 
> 5.46.. it's displaying 5.46
>
>
> ??!?@@$??
>
>
> -- 
>
> Steven Green
> Myrtle Beach, South Carolina, USA
>
> http://www.OasisTradingPost.com
>
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too 


Copyright © 2004 thedbcommunity.com